Propovoice: All-in-One Client Management System for WordPress through version 1.7.6.7 contains an arbitrary file-read vulnerability in the send_email() function. Unauthenticated attackers can read arbitrary files from the server.
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 provides a proof-of-concept exploit for CVE-2025-8422, targeting the Propovoice WordPress plugin (versions <= 1.7.6.7). The exploit leverages an unauthenticated arbitrary file read vulnerability in the plugin's send_email() function, accessible via the /wp-json/ndpv/v1/send-email REST API endpoint. The exploit is implemented in Python (cve-2025-8422-exploit.py) and allows an attacker to specify a target URL, an email recipient, and an optional file path to read. If successful, the server sends the contents of the specified file as an email attachment to the attacker-controlled address. The script can attempt to read multiple sensitive files, such as wp-config.php, /etc/passwd, and various log files. The repository consists of two files: a detailed README.md describing the vulnerability and usage, and the Python exploit script. The exploit does not require authentication and is effective against vulnerable plugin versions with the REST API exposed.
2 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.