Loading vulnerability…
CVE-2025-30567 is a path traversal vulnerability in the wp01ru WP01 product. The issue is described as an improper limitation of a pathname to a restricted directory, allowing an attacker to traverse directories outside the intended restricted path. The vulnerability affects WP01 through version 2.6.2. No additional technical detail about the specific vulnerable function, request parameter, or code path is provided in the available content.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository contains a proof-of-concept exploit (Poc_CVE-2025-30567.py) for CVE-2025-30567, an unauthorized arbitrary file download vulnerability in the WordPress WP01 plugin (version 2.6.2). The exploit is implemented as a Pocsuite3 module and demonstrates how an unauthenticated attacker can trigger the vulnerable AJAX action (wp01_generate_zip_archive) to create a zip archive of any file on the server (e.g., /etc/passwd), which is then made available for download from a predictable location (/wp-content/wp01-backup/wp-01-passwd.zip). The repository also includes the full source code of the WP01 plugin, which is used for analysis and demonstration purposes. The exploit leverages a lack of authorization checks in the make_archive method, allowing arbitrary file access via crafted POST requests. The main attack vector is network-based, targeting WordPress sites with the vulnerable plugin installed. The repository is structured with the PoC script at the root, the plugin source under the 'wp01' directory, and supporting assets and documentation.
4 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.