CVE-2026-3772

WP Editor <= 1.2.9.2 - Cross-Site Request Forgery to Remote Code Execution via Plugin and Theme File Editor

2026-04-30 00:00
AlexHenry

Strategic Overview

Status
Patched in 1.2.9.3
Affected Plugin
WP Editor
Affected Version
<= 1.2.9.2
CVSS
8.8High
Weakness type
CWE-352 · Cross-Site Request Forgery (CSRF)
CVE
CVE-2026-3772
View all WP Editor vulnerabilities

At a glance

CVE-2026-3772 is a high-severity Cross-Site Request Forgery (CSRF) vulnerability in the WP Editor WordPress plugin, affecting versions <= 1.2.9.2. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 1.2.9.3; sites on affected versions should update now. Disclosed April 2026, reported by AlexHenry.

Vulnerability Overview

The WP Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 1.2.9.2. This is due to missing nonce verification in the 'add_plugins_page' and 'add_themes_page' functions. This makes it possible for unauthenticated attackers to overwrite arbitrary plugin and theme PHP files with attacker-controlled code via a forged request, granted they can trick a site administrator into performing an action such as clicking a link.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-352: Cross-Site Request Forgery (CSRF)

WP Editor <= 1.2.9.2 carries this weakness at add_plugins_page, and reaching it takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.

An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WP Editor the fix is 1.2.9.3: builds <= 1.2.9.2 are affected, anything from 1.2.9.3 onward is not.

Remediation

Update to version 1.2.9.3, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WP Editor: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WP Editor 1.2.9.3 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2026-3772https://www.wordfence.com/threat-intel/vulnerabilities/id/b1bc4a87-d5de-4d66-9cc5-802ef11f886chttps://nvd.nist.gov/vuln/detail/CVE-2026-3772

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C