Skip to main content
CVE-2025-29894VulnerabilityPublished

CVE-2025-29894: QNAP Systems Qsync Central · SQL Injection

Affects QNAP Systems Qsync CentralSource CVE Database V5

0

Not known to be exploited · CVSS 7.5 High · fixed in 4.5.0.7 : patch QNAP Systems Qsync Central soon.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 4.0 base score
7.5High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 40% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 4.5.0.7
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 29 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

AI-suggested

European organizations should immediately verify their Qsync Central version and upgrade to 4.5.0.7 or later to remediate the vulnerability. Beyond patching, organizations should implement strict access controls and monitor user account activities for unusual behavior indicative of exploitation attempts. Employing Web Application Firewalls (WAFs) with SQL injection detection and prevention capabilities can provide an additional layer of defense. Regularly auditing and rotating credentials, enforcing multi-factor authentication (MFA) for all Qsync Central users, and limiting user privileges to the minimum necessary can reduce the risk of exploitation. Network segmentation should be used to isolate Qsync Central servers from critical infrastructure. Additionally, organizations should conduct vulnerability scanning and penetration testing focused on SQL injection vectors within their Qsync Central deployment. Incident response plans should be updated to include detection and containment strategies for SQL injection attacks targeting this product. Finally, logging and alerting mechanisms should be enhanced to capture suspicious database queries and anomalous command executions.

Description

An SQL injection vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to execute unauthorized code or commands. We have already fixed the vulnerability in the following version: Qsync Central 4.5.0.7 ( 2025/04/23 ) and later

References

Community reviews

Loading reviews…