How severe is CVE-2022-2446?

CVE-2022-2446 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.

Is CVE-2022-2446 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2022-2446?

CVE-2022-2446 affects Benjaminrojas Wp Editor. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2022-2446?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.

Does CVE-2022-2446 have an EU (EUVD) identifier?

Yes. CVE-2022-2446 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2022-34707.

When was CVE-2022-2446 published?

CVE-2022-2446 was published on 2024-09-13 and last updated on 2026-06-17.

CVE-2022-2446

CVE-2022-2446 is a high-severity vulnerability in Benjaminrojas Wp Editor with a CVSS 3.x base score of 7.2. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-502.

Key facts

Severity: High (CVSS 3.x base score 7.2)
EPSS exploit prediction: 1% (43rd percentile)
Actively exploited: Not listed in CISA KEV
EU (EUVD) id: EUVD-2022-34707
Weakness: CWE-502
Affected product: Benjaminrojas Wp Editor
Published: 2024-09-13
Last modified: 2026-06-17

Description

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 that the attacker is successful in uploading a file with the serialized payload.

Frequently asked questions

What is CVE-2022-2446?: 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 that the attacker is successful in uploading a file with the serialized payload.
How severe is CVE-2022-2446?: CVE-2022-2446 has a CVSS 3.x base score of 7.2, rated high severity. It is exploitable over network with low attack complexity, requires high privileges and no user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2022-2446 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (43rd percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2022-2446?: CVE-2022-2446 affects Benjaminrojas Wp Editor. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2022-2446?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
Does CVE-2022-2446 have an EU (EUVD) identifier?: Yes. CVE-2022-2446 is tracked in the ENISA EU Vulnerability Database (EUVD) as EUVD-2022-34707.
When was CVE-2022-2446 published?: CVE-2022-2446 was published on 2024-09-13 and last updated on 2026-06-17.

References

Affected products (1)

cpe:2.3:a:benjaminrojas:wp_editor:*:*:*:*:*:wordpress:*:*

More vulnerabilities in Benjaminrojas Wp Editor

CVE-2016-10886 — Critical (CVSS 9.8): The wp-editor plugin before 1.2.6 for WordPress has incorrect permissions.
CVE-2016-10885 — High (CVSS 8.8): The wp-editor plugin before 1.2.6 for WordPress has CSRF.
CVE-2025-3294 — High (CVSS 7.2): The WP Editor plugin for WordPress is vulnerable to arbitrary file update due to missing file path validation in all…
CVE-2021-24151 — High (CVSS 7.2): The WP Editor WordPress plugin before 1.2.7 did not sanitise or validate its setting fields leading to an authenticated…
CVE-2024-25591 — Medium (CVSS 5.3): Exposure of Sensitive Information to an Unauthorized Actor vulnerability in Benjamin Rojas WP Editor.This issue affects…
CVE-2025-3295 — Medium (CVSS 4.9): The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.2.9.1.…

All CVEs affecting Benjaminrojas Wp Editor →

Other CWE-502 (Deserialization of Untrusted Data) vulnerabilities

CVE-2026-41104 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Planetary Computer Pro allows an unauthorized attacker to disclose…
CVE-2026-43633 — Critical (CVSS 10.0): HestiaCP versions 1.9.0 through 1.9.4 contain a deserialization vulnerability in the web terminal component caused by a…
CVE-2026-33819 — Critical (CVSS 10.0): Deserialization of untrusted data in Microsoft Bing allows an unauthorized attacker to execute code over a network.
CVE-2026-20131 — Critical (CVSS 10.0): A vulnerability in the web-based management interface of Cisco Secure Firewall Management Center (FMC) Software could…
CVE-2026-25632 — Critical (CVSS 10.0): EPyT-Flow is a Python package designed for the easy generation of hydraulic and water quality scenario data of water…
CVE-2025-14931 — Critical (CVSS 10.0): Hugging Face smolagents Remote Python Executor Deserialization of Untrusted Data Remote Code Execution Vulnerability.…

Browse all CWE-502 (Deserialization of Untrusted Data) vulnerabilities →