Loading vulnerability…
A reflected cross-site scripting (XSS) vulnerability exists in the Shield Security WordPress plugin prior to version 20.0.6. The vulnerability is due to insufficient sanitization and escaping of a parameter that is output back to the page, allowing an attacker to inject arbitrary JavaScript code. This can be exploited by tricking high-privilege users, such as administrators, into clicking a crafted link.
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 Python proof-of-concept exploit for CVE-2024-7313, a reflected XSS vulnerability in the Shield Security Plugin for WordPress (versions below 20.0.6). The repository consists of a README.md (detailed usage and vulnerability info) and exploit.py (the main exploit script). The exploit works by checking if the target WordPress site is running a vulnerable version of the plugin, then generating a malicious URL containing a JavaScript XSS payload. When an administrator clicks this URL, the payload executes in their browser, automatically creating a new administrator account with attacker-supplied details and a hardcoded password. The exploit leverages endpoints such as /wp-login.php (for version checking), /wp-admin/user-new.php (for nonce retrieval and user creation), and injects the payload via the nav_sub parameter of /wp-admin/admin.php. The attack vector is browser-based, requiring social engineering to get an admin to click the crafted link. The exploit is a functional PoC and does not include advanced features or automation beyond payload generation.
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.