The PZ Frontend Manager WordPress plugin before version 1.0.6 lacks proper Cross-Site Request Forgery (CSRF) checks in certain areas. This allows an attacker to craft malicious requests that, if executed by an authenticated user, can result in unintended actions being performed on their behalf within the WordPress site.
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 (1 hidden).
This repository contains a Python exploit script (CVE-2024-6244.py) and a README.md for CVE-2024-6244, a CSRF vulnerability in the WordPress plugin pz-frontend-manager (versions <= 1.0.5). The exploit script first checks if the target WordPress site is running a vulnerable version by fetching the plugin's readme.txt. It then encodes a user-supplied image in Base64, logs in using provided credentials, and sends a crafted POST request to /wp-admin/admin-ajax.php to change the profile picture of the specified user (userID=1 by default). The script outputs the URL of the uploaded image if successful. The README provides usage instructions, requirements, and a description of the vulnerability. The main attack vector is web-based, targeting WordPress admin endpoints. The script is operational and requires valid credentials to execute the exploit.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
1 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.