HomeWordPress vulnerabilitiesWP Editor
WP Editor vulnerabilities
WP Editor has 8 known vulnerabilities in this database. The most recent published record is dated 1 May 2026.
- Known vulnerabilities
- 8
- Active installs
- 20,000+
- Latest version
- 1.2.9.3
- Last updated
- 11 Mar 2026
- Most recent
- 1 May 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site request forgery (CSRF) CVE-2026-3772 | High 8.8 | Up to 1.2.9.2 | Fixed in a later version (latest 1.2.9.3) | 1 May 2026 |
| Arbitrary file read CVE-2025-3295 | Medium 4.9 | Before 1.2.9.2 | Fixed in 1.2.9.2 | 17 Apr 2025 |
| Remote code execution CVE-2025-3294 | High 7.2 | Before 1.2.9.2 | Fixed in 1.2.9.2 | 17 Apr 2025 |
| PHP object injection CVE-2022-2446 | High 7.2 | Before 1.2.9.1 | Fixed in 1.2.9.1 | 13 Sep 2024 |
| SQL injection CVE-2021-24151 | High 7.2 | Before 1.2.7 | Fixed in 1.2.7 | 16 Jan 2024 |
| Cross-site request forgery (CSRF) CVE-2016-10885 | High 8.8 | Before 1.2.6 | Fixed in 1.2.6 | 14 Aug 2019 |
| Security weakness CVE-2016-10886 | Critical 9.8 | Before 1.2.6 | Fixed in 1.2.6 | 14 Aug 2019 |
| Cross-site scripting (XSS) CVE-2016-10877 | Medium 6.1 | Before 1.2.6.3 | Fixed in 1.2.6.3 | 12 Aug 2019 |
Read the published descriptions
- CVE-2026-3772, 1 May 2026
- 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. CVE record
- CVE-2025-3295, 17 Apr 2025
- The WP Editor plugin for WordPress is vulnerable to arbitrary file read in all versions up to, and including, 1.2.9.1. This makes it possible for authenticated attackers, with Administrator-level access and above, to read arbitrary files on the affected site's server which may reveal sensitive information. CVE record
- CVE-2025-3294, 17 Apr 2025
- The WP Editor plugin for WordPress is vulnerable to arbitrary file update due to missing file path validation in all versions up to, and including, 1.2.9.1. This makes it possible for authenticated attackers, with Administrator-level access and above, to overwrite arbitrary files on the affected site's server which may make remote code execution possible assuming the files can be written to by the web server. CVE record
- CVE-2022-2446, 13 Sep 2024
- 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. CVE record
- CVE-2021-24151, 16 Jan 2024
- The WP Editor WordPress plugin before 1.2.7 did not sanitise or validate its setting fields leading to an authenticated (admin+) blind SQL injection issue via an arbitrary parameter when making a request to save the settings. CVE record
- CVE-2016-10885, 14 Aug 2019
- The wp-editor plugin before 1.2.6 for WordPress has CSRF. CVE record
- CVE-2016-10886, 14 Aug 2019
- The wp-editor plugin before 1.2.6 for WordPress has incorrect permissions. CVE record
- CVE-2016-10877, 12 Aug 2019
- The wp-editor plugin before 1.2.6.3 for WordPress has multiple XSS issues. CVE record
What to do if you run WP Editor
If you run WP Editor, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP Editor vulnerabilities
Free. We email you when a new vulnerability is published for WP Editor, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.