CVE-2026-3772: The WP Editor plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to
Source GCVE Database
Not known to be exploited · CVSS 8.8 High.
Data as of 27 Oct 2026, 00:07 UTC
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 1 May 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| benjaminprojasWP Editor | Affected
| Fixed in– |
Description
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.
References
- nvd.nist.gov/vuln/detail/CVE-2026-3772 (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-editor/trunk/classes/WPEditorPlugins.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/wp-editor/trunk/classes/WPEditorThemes.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset/3480577 (opens in a new tab)
- wordfence.com/threat-intel/vulnerabilities/id/b1bc4a87-d5de-4d66-9cc5-802ef11f886c?source=cve (opens in a new tab)