CVE-2025-7431 is a stored cross-site scripting vulnerability in the Knowledge Base plugin for WordPress affecting all versions up to and including 2.3.1. The flaw is caused by insufficient input sanitization and output escaping of the plugin slug setting. An authenticated attacker with administrator-level access can inject arbitrary JavaScript or other web script payloads into stored content associated with that setting. The payload executes when a user accesses a page containing the injected content. According to the available information, the issue is limited to WordPress multisite installations and to installations where the unfiltered_html capability has been disabled.
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 documents a proof-of-concept (PoC) exploit for CVE-2025-7431, a stored cross-site scripting (XSS) vulnerability in the Knowledge Base plugin for WordPress (versions 2.3.1 and below). The exploit requires an authenticated attacker (Contributor or Administrator) to inject a malicious shortcode payload into the plugin's 'Slug' field via the admin dashboard. When another user accesses the 'All Articles' view, the injected JavaScript executes, leading to persistent XSS. The repository contains two markdown files (README.md and report.md) that describe the vulnerability, exploitation steps, and security impact. No executable code is present; the PoC is a manual exploitation guide with a sample payload. The main attack vector is authenticated web access to the WordPress admin panel, and the exploit targets the Knowledge Base plugin's settings interface.
4 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.