The Zephyr Project Manager WordPress plugin before version 3.3.99 fails to properly sanitize and escape certain settings. This flaw allows high privilege users, such as editors and admins, to inject malicious scripts (Stored Cross-Site Scripting) into the application, even when the unfiltered_html capability is disabled, as is common in WordPress multisite environments.
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 proof-of-concept exploit for CVE-2024-6536, a stored XSS vulnerability in the Zephyr Project Manager plugin for WordPress. The exploit requires valid credentials for a user with Zephyr Admin privileges. The script performs the following steps: (1) authenticates to the WordPress site, (2) retrieves a nonce required for project creation, and (3) creates a new project with a malicious JavaScript payload in the project name. If successful, the script outputs a URL to the malicious project, which, when visited by an admin, will trigger the XSS payload. The repository consists of the main exploit script (CVE-2024-6536.py) and a README.md with usage instructions and references. The exploit targets web endpoints specific to WordPress and the Zephyr Project Manager plugin.
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.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
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.