CSRF to RCE in WordPress Theme Editor plugin
CVE-2025-9890 affects the Theme Editor plugin for WordPress in all versions up to and including 3.0. The vulnerability is a Cross-Site Request Forgery issue caused by missing or incorrect nonce validation on the 'theme_editor_theme' page. Because the affected action does not properly verify request authenticity, an attacker can induce a privileged WordPress administrator to submit a forged request. In the context of a theme editor component, successful exploitation can result in unauthorized modification of theme files, leading to remote code execution on the WordPress server.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Recent activity
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
The version that knows your environment.
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.