Theme Editor · Security record
Is Theme Editor safe?
One known vulnerability affects the current version (3.2), and it has no fix yet.
Checked 4 days ago against the WPVulnerability database, for version 3.2.
How it’s looked after
- Last release
- Mar 19, 2026 (7 months ago)
- Releases in the last year
- 0
- Tested up to
- WordPress 6.9.11 (current: 7.1)
- Support resolved
- 0 of 1 threads in two months
- Active installs
- 50K+
10 known vulnerabilities
- 1 critical
- 3 high
- 2 medium
- 4 not rated
1 affects the current version. 1 has no fix yet.
Disclosed each year
- 20192
- 20212
- 20231
- 20241
- 20251
- 20262
Every known vulnerability in Theme Editor
Newest first, with any that affect the current version at the top.
- critical
Cross-Site Request Forgery
Affects the current version · No fix yet · CVE-2026-39640 · Feb 14, 2026 · Wordfence
Fixed in 3.2 · CVE-2025-14469 · Jul 31, 2026 · Wordfence
Fixed in 3.1 · CVE-2025-9890 · Oct 17, 2025 · Wordfence
Fixed in 2.9 · CVE-2022-2440 · Aug 28, 2024 · Wordfence
Fixed in 2.8 · CVE-2023-6091 · Nov 20, 2023 · Wordfence
Fixed in 2.6 · Feb 13, 2021 · Patchstack
Fixed in 2.6 · CVE-2021-24154 · Feb 13, 2021 · Wordfence
Fixed in 2.2 · Sep 30, 2019 · Wordfence
Fixed in 2.2 · Sep 30, 2019 · Patchstack
Fixed in 2.2 · WPScan
Questions about Theme Editor’s security
Is Theme Editor safe to use?
Yes: 1 known vulnerability affects version 3.2, according to WPVulnerability’s database. Until a fixed version is out, weigh the risk, or switch to an alternative.
Does Theme Editor have known security vulnerabilities?
Yes: 1 known vulnerability affects version 3.2, according to WPVulnerability’s database.
Is Theme Editor still maintained?
Its last release was 7 months ago. Its authors resolved 0 of the 1 support threads opened in the last two months.
Is Theme Editor compatible with the latest WordPress?
Theme Editor’s readme says it’s tested up to WordPress 6.9.11, while the current version is 7.1. That doesn’t mean it breaks, but its author hasn’t confirmed it works with the latest releases.
Hear about the next one first
Track your plugin on TrackWP and get an alert when a new vulnerability affecting it is published. Every plan has it, the free Starter too; Boost and FullCharge email it at once.
Start freeVulnerability data from WPVulnerability (CC0), which gathers records from CVE, Wordfence, Patchstack and WPScan. A clean record isn’t a guarantee: keep every plugin updated.