Is Theme Editor safe to use?

Laskyr does not give safety verdicts. The latest version (3.2) has 1 known unpatched vulnerability. As of 2026-11-04, the sources we check list the newest release of Theme Editor as affected and name no fixed version yet. Keep Theme Editor on the latest version (3.2) and remove it if you do not use it.

Which versions of Theme Editor are vulnerable?

Known issues on record (newest first): Cross-site request forgery (CSRF) (3.1 and older); Cross-site request forgery (CSRF) (3.2 and older); Cross-site request forgery (CSRF) (3.0 and older); PHP object injection (2.8 and older); Arbitrary file upload (2.7.1 and older, fixed in 2.8); Security issue (older than 2.6, fixed in 2.6). The full list with sources is on this page.

What is the latest version of Theme Editor?

3.2, according to wordpress.org (last updated 2026-03-19). It has 50,000+ active installs.

What should I do if my Theme Editor is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update theme-editor). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · theme-editor · data as of 2026-11-04

Is Theme Editor safe? Known vulnerabilities and latest version

Latest version: 3.2
Last updated: 2026-03-19
Active installs: 50,000+
Known issues on record: 6
Unpatched in latest: 1
Tested up to WP: 6.9.11 · PHP 5.2.4+

Theme Editor allows you to edit theme files, create folder, upload files and remove any file and folder in themes and plugins. — by mndpsingh287

What to do

There is no fixed version yet. If you can live without Theme Editor for now, deactivate it and delete it until the developer ships a fix.
If you must keep it, limit who can log in (remove unused accounts, especially low-level ones) and put a web application firewall in front of the site.
Watch for an update: get an email when this page changes.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI: wp plugin get theme-editor --field=version shows what you run; wp plugin update theme-editor updates it.

Check your version

Known vulnerabilities

6 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version.

medium 4.3 CVE-2025-14469 · published 2026-08-01

Cross-site request forgery (CSRF) in Theme Editor (3.1 and older)

Affected: 3.1 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-14469 Wordfence advisory wordpress.org Plugin source

critical 9.6 affects latest 3.2 CVE-2026-39640 · published 2026-04-08

Cross-site request forgery (CSRF) in Theme Editor (3.2 and older)

Affected: 3.2 and older
Fixed in: no fix listed yet
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Cross-Site Request Forgery (CSRF) vulnerability in mndpsingh287 Theme Editor theme-editor allows Code Injection.This issue affects Theme Editor: from n/a through <= 3.2.

NVD CVE-2026-39640 Patchstack advisory

high 8.8 CVE-2025-9890 · published 2025-10-18

Cross-site request forgery (CSRF) in Theme Editor (3.0 and older)

Affected: 3.0 and older
Fixed in: unknown
Access needed (per CVSS): No login needed; someone on the site has to click a link or open a page
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2025-9890 Wordfence advisory Code change (fix)Plugin source

high 7.2 CVE-2022-2440 · published 2024-08-29

PHP object injection in Theme Editor (2.8 and older)

Affected: 2.8 and older
Fixed in: unknown
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2022-2440 Wordfence advisory Code change (fix)Plugin source

high 7.2 CVE-2023-6091 · published 2024-03-26

Arbitrary file upload in Theme Editor (2.7.1 and older)

Affected: 2.7.1 and older
Fixed in: 2.8
Access needed (per CVSS): Needs an admin-level account
Range from: CVE record (the advisory publisher) · score by Patchstack

Details from the advisory

Unrestricted Upload of File with Dangerous Type vulnerability in mndpsingh287 Theme Editor.This issue affects Theme Editor: from n/a through 2.7.1.

NVD CVE-2023-6091 Patchstack advisory

medium 4.9 CVE-2021-24154 · published 2021-04-05

Security issue in Theme Editor (older than 2.6)

Affected: older than 2.6
Fixed in: 2.6
Access needed (per CVSS): Needs an admin-level account
Range from: NVD analysis · score by NVD

Details from the advisory

The Theme Editor WordPress plugin before 2.6 did not validate the GET file parameter before passing it to the download_file() function, allowing administrators to download arbitrary files on the web server, such as /etc/passwd

NVD CVE-2021-24154 WPScan advisory

Recent activity

2026-03-19 — latest release on wordpress.org (3.2).
2026-08-01 — Cross-site request forgery (CSRF) disclosed (CVE-2025-14469), fix version not stated.
2026-04-08 — Cross-site request forgery (CSRF) disclosed (CVE-2026-39640), no fix listed yet.
2025-10-18 — Cross-site request forgery (CSRF) disclosed (CVE-2025-9890), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for Theme Editor (theme-editor) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Cross-site request forgery (CSRF) (3) · PHP object injection (1) · Arbitrary file upload (1)

Where this data comes from

Version, last update, installs: wordpress.org/plugins/theme-editor (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/theme-editor"><img src="https://laskyr.com/plugins/theme-editor/badge.svg" alt="Theme Editor vulnerability status"></a>

← Check another plugin · Free hacked-site scan

Is Theme Editor safe? Known vulnerabilities and latest version

The latest version (3.2) has 1 known unpatched vulnerability

What to do

Check your version

Known vulnerabilities

Cross-site request forgery (CSRF) in Theme Editor (3.1 and older)

Cross-site request forgery (CSRF) in Theme Editor (3.2 and older)

Cross-site request forgery (CSRF) in Theme Editor (3.0 and older)

PHP object injection in Theme Editor (2.8 and older)

Arbitrary file upload in Theme Editor (2.7.1 and older)

Security issue in Theme Editor (older than 2.6)

Recent activity

Get an email when Theme Editor has a new vulnerability

Browse vulnerabilities

Where this data comes from