CVE-2015-9357 is a cross-site scripting (XSS) vulnerability in the Akismet plugin for WordPress, affecting versions prior to 3.1.5. The vulnerability allows attackers to inject arbitrary web scripts or HTML via unspecified vectors, which are then executed in the context of users visiting affected WordPress sites.
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 is a small standalone Python proof-of-concept exploit for CVE-2015-9357, containing one executable script and a README. The main file, CVE-2015-9357-poc.py, automates a stored XSS-to-admin-takeover chain against vulnerable WordPress input handling that performs smiley/emoticon parsing. The script starts a local HTTP listener, crafts an HTML/JavaScript payload that breaks out of an attribute context, and submits that payload to an operator-specified vulnerable endpoint and field. When an authenticated administrator later views the stored content, the injected JavaScript runs in the admin's browser, requests /wp-admin/user-new.php, extracts the create-user nonce, sends that nonce back to the attacker listener, and then submits a forged POST to create a new administrator account with hardcoded credentials: pwned / Password123! / pwned@evil.com. After receiving the nonce, the Python script waits briefly and then attempts to authenticate to /wp-login.php to confirm successful account creation. The exploit is operational rather than a mere detection script because it performs end-to-end exploitation and account creation, but it uses a basic hardcoded payload and requires manual knowledge of the vulnerable submission endpoint and field. The README explains the attack chain, usage syntax, and the dependency on a target field that actually undergoes WordPress smiley conversion.
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.