Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-8385: CWE-22 Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') in PX-lab Zombify

0
Medium
VulnerabilityCVE-2025-8385cvecve-2025-8385cwe-22
Published: Fri Oct 31 2025 (10/31/2025, 07:26:40 UTC)
Source: CVE Database V5
Vendor/Project: PX-lab
Product: Zombify

Description

The Zombify plugin for WordPress is vulnerable to Path Traversal in all versions up to, and including, 1.7.5. This is due to insufficient input validation in the zf_get_file_by_url function. This makes it possible for authenticated attackers, with subscriber-level access and above, to read arbitrary files on the server, including sensitive system files like /etc/passwd, via a forged request. It's worth noting that successfully exploiting this vulnerability relies on a race condition as the file generated will be deleted immediately.

AI-Powered Analysis

AILast updated: 10/31/2025, 07:41:06 UTC

Technical Analysis

CVE-2025-8385 is a path traversal vulnerability classified under CWE-22 affecting the PX-lab Zombify plugin for WordPress, versions up to and including 1.7.5. The root cause is insufficient input validation in the zf_get_file_by_url function, which fails to properly restrict file pathnames to authorized directories. This flaw allows an authenticated attacker with subscriber-level privileges or higher to manipulate file path parameters to access arbitrary files on the server filesystem. The vulnerability is exploitable remotely over the network without user interaction but requires authentication at a low privilege level. A race condition is involved because the plugin generates a temporary file that is deleted immediately, so the attacker must time the request precisely to read the file contents before deletion. The impact is primarily on confidentiality, as attackers can read sensitive system files such as /etc/passwd, potentially leading to further attacks or information disclosure. The CVSS 3.1 base score of 6.8 reflects medium severity, with high attack complexity due to the race condition, no integrity or availability impact, and a scope change since the vulnerability affects the underlying system beyond the plugin itself. No patches or known exploits have been reported at the time of publication, but the vulnerability poses a significant risk to WordPress sites using this plugin if left unmitigated.

Potential Impact

For European organizations, this vulnerability could lead to unauthorized disclosure of sensitive system files and configuration data, potentially exposing user credentials, system configurations, or other confidential information. This exposure could facilitate further attacks such as privilege escalation, lateral movement, or targeted exploitation of other vulnerabilities. Organizations relying on WordPress sites with the PX-lab Zombify plugin are at risk of data breaches and compliance violations, especially under GDPR regulations that mandate protection of personal data. The requirement for authenticated access lowers the risk somewhat but does not eliminate it, as subscriber-level accounts are common and may be compromised or created by attackers. The race condition adds complexity to exploitation but does not prevent it. The vulnerability does not impact system integrity or availability directly but compromises confidentiality, which can have cascading effects on organizational security posture.

Mitigation Recommendations

1. Immediately upgrade the PX-lab Zombify plugin to a version that addresses this vulnerability once available. 2. Until a patch is released, restrict subscriber-level access and review user roles to minimize the number of users with such privileges. 3. Implement web application firewall (WAF) rules to detect and block suspicious path traversal patterns targeting the zf_get_file_by_url function. 4. Monitor server logs for unusual file access attempts or race condition exploitation patterns. 5. Harden the server filesystem permissions to limit the plugin’s ability to access sensitive files outside its intended directories. 6. Employ intrusion detection systems (IDS) to alert on anomalous file read operations. 7. Conduct regular security audits of WordPress plugins and remove or replace those that are unmaintained or vulnerable. 8. Educate administrators and users about the risks of low-privilege account compromise and enforce strong authentication mechanisms.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
Wordfence
Date Reserved
2025-07-30T18:45:04.999Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6904678cd694fb7fc736cf50

Added to database: 10/31/2025, 7:38:52 AM

Last enriched: 10/31/2025, 7:41:06 AM

Last updated: 11/1/2025, 3:49:22 PM

Views: 16

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats