CVE-2022-2275: The WP Edit Menu WordPress plugin before 1.5.0 does not have CSRF in an AJAX action, which could allow attacke
CVE-2022-2275 is a medium-severity flaw (CVSS 4.3) affecting wp edit menu. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The WP Edit Menu WordPress plugin before 1.5.0 does not have CSRF in an AJAX action, which could allow attackers to make a logged in admin delete arbitrary posts/pages from the blog via a CSRF attack
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 4.3 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.3% (top 72%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-08-22 |
| Last modified | 2026-06-17 |
Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score
Am I affected?
Timeline
- Published CVE record published
- Updated Record last modified
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.
Quick answers
How do I fix CVE-2022-2275?
wp edit menu: upgrade to 1.5.0. Exact commands for each OS are on this page.
Is CVE-2022-2275 being exploited?
CVE-2022-2275 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.
What does CVE-2022-2275 affect?
CVE-2022-2275 affects wp edit menu. Severity is medium (CVSS 4.3). The WP Edit Menu WordPress plugin before 1.5.0 does not have CSRF in an AJAX action, which could allow attackers to make a logged in admin delete arbitrary posts/pages from the blog via a CSRF attack
How urgent is CVE-2022-2275?
Priority 27/100. Public exploit reference
Software pages
Related CVEs
- CVE-2022-2276 MEDIUM 4.3 UPGRADE The WP Edit Menu WordPress plugin before 1.5.0 does not have authorisation and CSRF in an AJAX action, which c