CVE-2022-2446: The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_

Q: How do I fix CVE-2022-2446?

wp editor: upgrade to 1.2.9.1. Exact commands for each OS are on this page.

Q: Is CVE-2022-2446 being exploited?

CVE-2022-2446 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

Q: What does CVE-2022-2446 affect?

CVE-2022-2446 affects wp editor. Severity is high (CVSS 7.2). The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_root' parameter in versions up to, and including 1.2.9. This makes it possible for authenticated attackers with administrative pri

Routine

HIGH 7.2UPGRADE

CVE-2022-2446 is a high-severity flaw (CVSS 7.2) affecting wp editor. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_root' parameter in versions up to, and including 1.2.9. 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 t

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	7.2 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	High
User interaction	None
EPSS exploit chance	0.6% (top 52%)
CISA exploited list	No
Weakness	CWE-502
Published	2024-09-13
Last modified	2026-06-17

Publisher (CNA): Wordfence · Vendor: benjaminrojas

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

2024-09-13 15:15 UTCPublished CVE record published
2026-06-17 04:41 UTCUpdated Record last modified

benjaminrojas wp editor UPGRADE

Affected: < 1.2.9.1

Fixed in: 1.2.9.1

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy wp-editor || rpm -q wp-editor || wp-editor --version

2. UPGRADE to 1.2.9.1 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade wp-editor

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade wp-editor

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2022-2446?

wp editor: upgrade to 1.2.9.1. Exact commands for each OS are on this page.

Is CVE-2022-2446 being exploited?

CVE-2022-2446 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2022-2446 affect?

CVE-2022-2446 affects wp editor. Severity is high (CVSS 7.2). The WP Editor plugin for WordPress is vulnerable to deserialization of untrusted input via the 'current_theme_root' parameter in versions up to, and including 1.2.9. This makes it possible for authenticated attackers with administrative pri

How urgent is CVE-2022-2446?

Priority 37/100. High severity

Software pages

WordPress vulnerabilities · PHP vulnerabilities

Related CVEs

CVE-2025-3295 MEDIUM 4.9 UPGRADE The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including,
CVE-2025-3294 HIGH 7.2 UPGRADE The WP Editor plugin for WordPress is vulnerable to arbitrary file update due to missing file path validation
CVE-2024-25591 MEDIUM 5.3 UPGRADE Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Benjamin Rojas WP Editor.This issu

References

← Back to latest CVEs