Skip to main content
CVE-2024-41376VulnerabilityPublished

CVE-2024-41376: dzzoffice · n/a

Affects dzzofficeSource CVE Database V5

0

Not known to be exploited · CVSS 8.8 High.

Data as of 26 Oct 2026, 06:26 UTC

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

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 5 Aug 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 2026-10-26.

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

To mitigate CVE-2024-41376, organizations should implement the following specific measures: 1) Apply official patches or updates from dzzoffice as soon as they become available to address the directory traversal flaw. 2) In the interim, restrict access to the vulnerable user/space/about.php script using web server configurations or access control lists to limit exposure. 3) Implement strict input validation and sanitization on all user-supplied parameters to prevent traversal sequences such as '../'. 4) Employ web application firewalls (WAFs) with custom rules to detect and block directory traversal attempts targeting this endpoint. 5) Conduct thorough security audits and code reviews focusing on file path handling within the application. 6) Monitor logs for unusual file access patterns or errors indicative of traversal attempts. 7) Educate development teams on secure coding practices related to file system access. These targeted actions go beyond generic advice and directly address the vulnerability's exploitation vectors.

Description

dzzoffice 2.02.1 is vulnerable to Directory Traversal via user/space/about.php.

References

Community reviews

Loading reviews…