Skip to main content
CVE-2024-29273VulnerabilityPublished Updated

CVE-2024-29273: dzzoffice · n/a

Affects dzzofficeSource CVE Database V5

0

Not known to be exploited · CVSS 6.1 Medium.

Data as of 26 Oct 2026, 08:30 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Mar 2024

  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 26 Oct 2026.

What to do

Affected software

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

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

AI-suggested

Until an official patch is released, organizations should implement several specific mitigations: 1) Restrict file upload types strictly, disallowing SVG uploads or any file types that can contain executable scripts. 2) Employ server-side sanitization of SVG files to remove any embedded scripts or potentially dangerous XML elements before storage or rendering. 3) Implement Content Security Policy (CSP) headers to limit script execution sources and reduce the impact of XSS payloads. 4) Educate users to be cautious with unexpected or suspicious file uploads and links. 5) Monitor web server logs and application behavior for unusual upload activity or script execution attempts. 6) Consider deploying web application firewalls (WAFs) with rules to detect and block XSS payloads in uploads. 7) Isolate or sandbox the affected application environment to limit lateral movement if exploitation occurs. 8) Regularly review and update security controls related to file handling and input validation. These measures will reduce the risk of exploitation while awaiting an official fix from the vendor.

Description

There is Stored Cross-Site Scripting (XSS) in dzzoffice 2.02.1 SC UTF8 in uploadfile to index.php, with the XSS payload in an SVG document.

References

Community reviews

Loading reviews…