Skip to main content
CVE-2025-63694VulnerabilityPublished Updated

CVE-2025-63694: dzzoffice · n/a

Affects dzzofficeSource CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 26 Oct 2026, 06:26 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 31% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Nov 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-26.

What to do

Affected software

ProductAffectedFixed in
GitHubzyx0814/dzzofficepkg:github/zyx0814/dzzofficeOther threatsAffected
  • <=2.3.7
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately restrict network access to the explorer/groupmanage component of DzzOffice using firewall rules or network segmentation to limit exposure. 2. Deploy a web application firewall (WAF) with SQL Injection detection and prevention capabilities to block malicious payloads targeting this vulnerability. 3. Conduct thorough input validation and sanitization on all user inputs interacting with the groupmanage module, applying parameterized queries or prepared statements where possible. 4. Monitor database logs and application logs for unusual query patterns or error messages indicative of SQL Injection attempts. 5. Engage with DzzOffice vendors or community to obtain patches or security updates as soon as they become available and apply them promptly. 6. Implement intrusion detection systems (IDS) tuned to detect SQL Injection attack signatures. 7. Educate development and security teams about secure coding practices to prevent similar vulnerabilities in future releases. 8. Consider temporary disabling or isolating the vulnerable functionality if it is not critical to operations until a patch is applied.

Description

DzzOffice v2.3.7 and before is vulnerable to SQL Injection in explorer/groupmanage.

References

Community reviews

Loading reviews…