WordPress security by component
WP Editor
Plugin description
WP Editor is a WordPress component with 10 published CVE records in this archive. The latest tracked vulnerability was published May 01, 2026; the highest CVE/CNA score is 9.8.
Plugin slug:
wp-editorLatest vulnerability
CVE-2026-3772: WP Editor: Cross-site request forgery
WP Editor is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The published affected range is <= 1.2.9.2.
| Safe version |
|
||
|---|---|---|---|
| May 01, 2026 |
CVE-2026-3772
WP Editor: Cross-site request forgery
WP Editor is affected by cross-site request forgery. The vulnerable path is reachable without authentication. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request. The published affected range is <= 1.2.9.2.
|
> 1.2.9.2 |
CVE8.8
NVDPending
|
| Apr 17, 2025 |
CVE-2025-3295
WP Editor: Filesystem traversal
WP Editor is affected by filesystem traversal. Exploitation requires at least administrator-level access. A crafted path can escape the intended directory and reach files or directories elsewhere on the server.
|
See mitigation notes |
CVE4.9
NVDPending
|
| Apr 17, 2025 |
CVE-2025-3294
WP Editor: Code execution
WP Editor is affected by code execution. Exploitation requires at least administrator-level access. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE7.2
NVDPending
|
| Sep 13, 2024 |
CVE-2022-2446
WP Editor: Code execution
WP Editor is affected by code execution. Exploitation requires an authenticated WordPress account. Successful exploitation can run attacker-controlled code in the WordPress hosting account.
|
See mitigation notes |
CVE7.2
NVDPending
|
| Mar 27, 2024 |
CVE-2024-24700
WP Editor: Cross-site scripting
WP Editor is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE7.1
NVDPending
|
| Mar 17, 2024 |
CVE-2024-25591
WP Editor: A security weakness
WP Editor is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE5.3
NVD7.5
|
| Jan 16, 2024 |
CVE-2021-24151
WP Editor: SQL injection
WP Editor is affected by SQL injection. Exposure depends on how the affected operation is made reachable by the site. A successful request can alter database queries and expose or modify WordPress data.
|
See mitigation notes |
CVE7.2
NVD7.2
|
| Aug 14, 2019 |
CVE-2016-10886
Wp Editor: A security weakness
Wp Editor is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.
|
See mitigation notes |
CVE9.8
NVD9.8
|
| Aug 14, 2019 |
CVE-2016-10885
Wp Editor: Cross-site request forgery
Wp Editor is affected by cross-site request forgery. Exposure depends on how the affected operation is made reachable by the site. Exploitation relies on a signed-in privileged user submitting an attacker-controlled request.
|
See mitigation notes |
CVE8.8
NVD8.8
|
| Aug 12, 2019 |
CVE-2016-10877
Wp Editor: Cross-site scripting
Wp Editor is affected by cross-site scripting. Exposure depends on how the affected operation is made reachable by the site. Injected script can execute in the affected site's origin when the vulnerable output is viewed.
|
See mitigation notes |
CVE6.1
NVD6.1
|