HomeWordPress vulnerabilitiesTheme Editor
Theme Editor vulnerabilities
Theme Editor has 3 known vulnerabilities in this database. The most recent published record is dated 1 Aug 2026.
- Known vulnerabilities
- 3
- Active installs
- 50,000+
- Latest version
- 3.2
- Last updated
- 19 Mar 2026
- Most recent
- 1 Aug 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2025-14469 | Medium 4.3 | Up to 3.1 | Fixed in a later version (latest 3.2) | 1 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2025-9890 | High 8.8 | Up to 3.0 | Fixed in a later version (latest 3.2) | 18 Oct 2025 |
| PHP object injection CVE-2022-2440 | High 7.2 | Before 2.9 | Fixed in 2.9 | 29 Aug 2024 |
Read the published descriptions
- CVE-2025-14469, 1 Aug 2026
- 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. CVE record
- CVE-2025-9890, 18 Oct 2025
- The Theme Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 3.0. This is due to missing or incorrect nonce validation on the 'theme_editor_theme' page. This makes it possible for unauthenticated attackers to achieve remote code execution via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2022-2440, 29 Aug 2024
- The Theme Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'images_array' parameter in versions up to, and including 2.8. This makes it possible for authenticated attackers with administrative privileges to call files using a PHAR wrapper that will deserialize and call arbitrary PHP Objects that can be used to perform a variety of malicious actions granted a POP chain is also present. It also requires that the attacker is successful in uploading a file with the serialized payload. CVE record
What to do if you run Theme Editor
If you run Theme Editor, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Theme Editor vulnerabilities
Free. We email you when a new vulnerability is published for Theme Editor, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.