WordPress plugin · Updated daily · Source: Wordfence Intelligence

Theme Editor vulnerabilities: affected versions and fixes

Theme Editor has 50,000+ active installs. Here are its publicly disclosed vulnerabilities, whether your version is affected, and what to do now.

Theme Editor at a glance

  • 7 publicly disclosed vulnerabilities, 4 of them rated High or Critical. The most recent was disclosed on Jul 31, 2026.
  • Ranked #761 by popularity on WordPress.org (50,000+ active installs).
  • The latest version is 3.2 (released Mar 19, 2026). The most recent security fix shipped in 3.2.
  • 1 vulnerability has no fix yet. Check the list below to see whether it affects how you use the plugin.
  • The first thing to do: update to the latest version and turn on automatic updates.

Check your Theme Editor version

Enter the Theme Editor version number shown on your Plugins screen to see only the vulnerabilities that apply to it, most serious first.

Your version number is compared on this page only. It is not sent anywhere.

Get an email when a new vulnerability is disclosed

We'll tell you when a new vulnerability is disclosed in “Theme Editor”, with the version that fixes it. Free, email address only, stop any time.

We use your email address only for these alerts. Privacy policy

Want every plugin and theme on your site checked daily?

With Security Ready Standard, just install the “KazLinks Security Ready” plugin from WordPress.org. It sends only the names and versions of your plugins and themes, and we check them against disclosed vulnerabilities every day. Your first in-depth scan is free.

View the plugin on wordpress.orgGet a free in-depth scan

How to check whether your site is affected

  1. 1

    Find your version

    In your WordPress dashboard, open Plugins → Installed Plugins and look at the version number under “Theme Editor”.

  2. 2

    Compare it with the list below

    If your version falls within “Affected versions”, that vulnerability applies to you. If you are on the “Fixed in” version or later, it does not.

  3. 3

    Update

    Click “Update now” to move to the latest version (3.2). Taking a backup first is a good idea.

  4. 4

    Turn on automatic updates

    On the same screen, click “Enable auto-updates” so future fixes are installed automatically.

Known Theme Editor vulnerabilities

  • Theme Editor <= 3.1 - Cross-Site Request Forgery to CSS Modification

    Cross-site request forgery (CSRF) · CVE-2025-14469

    Affected versions: ≤ 3.1

    Fixed in: 3.2

    Severity: Medium 4.3 · Disclosed Jul 31, 2026

  • Theme Editor <= 3.2 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF) · CVE-2026-39640

    Affected versions: ≤ 3.2

    Fixed in: No fix yet

    Severity: Medium 4.3 · Disclosed Feb 14, 2026

  • Theme Editor <= 3.0 - Cross-Site Request Forgery to Remote Code Execution

    Cross-site request forgery (CSRF) · CVE-2025-9890

    Affected versions: ≤ 3.0

    Fixed in: 3.1

    Severity: High 8.8 · Disclosed Oct 17, 2025

  • Theme Editor <= 2.8 - Authenticated (Admin+) PHAR Deserialization

    PHP object injection · CVE-2022-2440

    Affected versions: ≤ 2.8

    Fixed in: 2.9

    Severity: High 7.2 · Disclosed Aug 28, 2024

  • Theme Editor <= 2.7.1 - Authenticated (Administrator+) Arbitrary File Upload

    Arbitrary file upload · CVE-2023-6091

    Affected versions: ≤ 2.7.1

    Fixed in: 2.8

    Severity: High 7.2 · Disclosed Nov 20, 2023

  • Theme Editor <= 2.5 - Authenticated Arbitrary File Download

    Other weakness · CVE-2021-24154

    Affected versions: ≤ 2.5

    Fixed in: 2.6

    Severity: Medium 4.9 · Disclosed Feb 13, 2021

  • Theme Editor <= 2.1 - Cross-Site Request Forgery

    Cross-site request forgery (CSRF)

    Affected versions: < 2.2

    Fixed in: 2.2

    Severity: High 8.8 · Disclosed Sep 30, 2019

Vulnerability data: Wordfence Intelligence (Copyright Defiant, Inc. · license terms). Severity is the CVSS score (0–10). Most recent disclosure: Jul 31, 2026.

Most common weaknesses in Theme Editor

Cross-site request forgery (CSRF)

4 issues

If an administrator who is logged in opens a booby-trapped page elsewhere, the site can be made to change settings without their knowledge.

PHP object injection

1 issue

Specially crafted data makes the server behave in unintended ways. Combined with the right conditions, it can lead to a full takeover.

Arbitrary file upload

1 issue

An attacker can upload a malicious file disguised as an image or document. Once it is on the server, it can be used to take over the site.

Frequently asked questions

Is Theme Editor safe to use?

Theme Editor is a well-known plugin with 50,000+ active installs. Finding vulnerabilities in popular plugins is common, and most of them are fixed in newer versions. The important thing is to stay on the latest version (3.2) and turn on automatic updates. That said, 1 issue has no fix yet, so check the list below.

How do I find which version of Theme Editor my site is running?

In your WordPress dashboard, go to Plugins → Installed Plugins. The version number is shown under the plugin name. If you see “There is a new version available”, you are on an older version.

Could updating break my site?

Occasionally an update changes how something looks or works, so take a backup before updating. If an agency or developer maintains your site, send them a link to this page and ask them to update.

Can I check all my other plugins too?

Yes. Security Ready reads the versions of every plugin and theme on your site, matches them against known vulnerabilities every day, and tells you what to fix. Your first in-depth scan is free.

Check every plugin and theme automatically, every day

Security Ready reads the versions of every plugin, theme and WordPress core on your site, matches them against known vulnerabilities every day, and tells you how to fix what it finds. Your first in-depth scan is free, and no payment details are needed.

Think your site has already been hacked? Before updating, read what to do in the first hour. Updating alone does not remove a backdoor that has already been planted.

← All plugin vulnerabilitiesTheme Editor on WordPress.org