CVE-2025-30263: QNAP Systems Qsync Central · CWE-476
Affects QNAP Systems Qsync CentralSource CVE Database V5
Not known to be exploited · CVSS 5.3 Medium · fixed in 5.0.0.0 : update QNAP Systems Qsync Central when convenient.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.4% chance of exploitation in 30 days – higher than 39% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.0.0
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:N/VA:L/SC:N/SI:N/SA:NExploitation evidence
Disclosed: evidence found.
CVE published 29 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
AI-suggested
European organizations should prioritize upgrading Qsync Central to version 5.0.0.0 or later, where the vulnerability is patched. Beyond patching, organizations should enforce strong user account security measures, including multi-factor authentication (MFA) to reduce the risk of account compromise. Regularly auditing user accounts and permissions can help detect and remove unauthorized or dormant accounts that could be exploited. Network segmentation and firewall rules should limit access to Qsync Central services to trusted internal networks or VPN users only, reducing exposure to remote attackers. Monitoring and alerting on unusual service crashes or DoS symptoms can provide early detection of exploitation attempts. Additionally, organizations should educate users on phishing risks to prevent credential theft that could lead to exploitation of this vulnerability.
Description
A NULL pointer dereference vulnerability has been reported to affect Qsync Central. If a remote attacker gains a user account, they can then exploit the vulnerability to launch a denial-of-service (DoS) attack. We have already fixed the vulnerability in the following version: Qsync Central 5.0.0.0 ( 2025/06/13 ) and later