Theme Editor <= 3.1 - Cross-Site Request Forgery to CSS Modification
Strategic Overview
- Status
- Patched in 3.2
- Affected Plugin
- Theme Editor
- Affected Version
<= 3.1- CVSS
- 4.3Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-14469
At a glance
CVE-2025-14469 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the Theme Editor WordPress plugin, affecting versions <= 3.1. It carries a CVSS score of 4.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.2; sites on affected versions should update now. Disclosed July 2026, reported by Nabil Irawan.
Vulnerability Overview
The Theme Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.1. This is due to missing nonce validation on the ms_update AJAX action. This makes it possible for unauthenticated attackers to modify child theme CSS styles via a forged request granted they can trick an administrator into performing an action such as clicking on a link.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in Theme Editor <= 3.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For Theme Editor the fix is 3.2: builds <= 3.1 are affected, anything from 3.2 onward is not.
Remediation
Update to version 3.2, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Theme Editor: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Theme Editor 3.2 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C