WordPress plugin
Theme Editor security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High4
- Medium3
- Low0
All Theme Editor vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.8 | Cross-Site Request Forgery to Remote Code Execution ≤3.0Update to 3.1 | CVE-2025-9890 | |
| High7.2 | Authenticated (Admin+) PHAR Deserialization ≤2.8Update to 2.9 | CVE-2022-2440 | |
| High7.2 | Authenticated (Administrator+) Arbitrary File Upload ≤2.7.1Update to 2.8 | CVE-2023-6091 | |
| High8.8 | Cross-Site Request Forgery <2.2Update to 2.2 | — |
- High8.8Cross-Site Request Forgery to Remote Code Execution
≤3.0Update to 3.1
- High7.2Authenticated (Admin+) PHAR Deserialization
≤2.8Update to 2.9
- High7.2Authenticated (Administrator+) Arbitrary File Upload
≤2.7.1Update to 2.8
- High8.8Cross-Site Request Forgery
<2.2Update to 2.2
Theme Editor: common questions
Does Theme Editor have known vulnerabilities?
Yes. VulnCrest Radar lists 7 known vulnerabilities in Theme Editor: 4 high, 3 medium. At least one is not fixed in the latest version.
How do I check which version of Theme Editor I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Theme Editor vulnerability?
CVE-2025-14469, published Jul 31, 2026: Theme Editor <= 3.1 - Cross-Site Request Forgery to CSS Modification. Severity: Medium (CVSS 4.3).
Is any Theme Editor vulnerability listed in CISA KEV?
No. None of the known Theme Editor vulnerabilities is currently listed in the CISA KEV catalog.