Skip to main content
CVE-2024-55529VulnerabilityPublished

CVE-2024-55529: Z-Blog- · n/a

Affects Z-Blog-Source CVE Database V5

0

Not known to be exploited · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.6% chance of exploitation in 30 days – higher than 49% 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 6 Jan 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
GitHubfengyijiu520/Z-Blog-pkg:github/fengyijiu520/Z-Blog-Other threatsAffected
  • =1.7.3
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 the following mitigations: 1) Restrict access to the \zb_users\theme\shell\template directory via web server configuration (e.g., deny all HTTP requests to this path). 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious requests targeting this component. 3) Monitor web server logs for unusual or unauthorized access attempts to the vulnerable path. 4) Isolate the Z-BlogPHP server within a segmented network zone to limit lateral movement if compromised. 5) Regularly back up website data and configurations to enable recovery in case of compromise. 6) Stay alert for official patches or updates from Z-BlogPHP developers and apply them immediately upon release. 7) Consider temporary removal or disabling of vulnerable themes or plugins if feasible. These targeted actions go beyond generic advice and focus on mitigating the specific attack vector until a fix is available.

Description

Z-BlogPHP 1.7.3 is vulnerable to arbitrary code execution via \zb_users\theme\shell\template.

References

Community reviews

Loading reviews…