Skip to main content
CVE-2025-63695VulnerabilityPublished Updated

CVE-2025-63695: 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:15 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 35% 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-25.

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

To mitigate CVE-2025-63695, organizations should immediately upgrade DzzOffice to a patched version once available. In the absence of an official patch, implement the following measures: 1) Restrict file upload directories with strict permissions to prevent execution of uploaded files; 2) Employ web application firewalls (WAFs) to detect and block suspicious file upload attempts; 3) Implement server-side validation to enforce allowed file types and reject potentially dangerous files; 4) Disable or limit the UEditor file upload feature if not essential; 5) Monitor logs for unusual file upload activity or web requests targeting /dzz/system/ueditor/php/controller.php; 6) Conduct regular security assessments and penetration testing focusing on file upload functionalities; 7) Isolate DzzOffice instances in segmented network zones to limit potential lateral movement; 8) Educate administrators on the risks and ensure timely application of security updates. These targeted actions go beyond generic advice and address the specific attack vector and environment of this vulnerability.

Description

DzzOffice v2.3.7 and before is vulnerable to Arbitrary File Upload in /dzz/system/ueditor/php/controller.php.

References

Community reviews

Loading reviews…