PatchTheCVECVE-2022-1843: The MailPress WordPress plugin through 7.2.1 does not have CSRF checks in various places, which could allow at
CVE-2022-1843 is a medium-severity flaw (CVSS 6.5) affecting mailpress. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The MailPress WordPress plugin through 7.2.1 does not have CSRF checks in various places, which could allow attackers to make a logged in admin change the settings, purge log files and more via CSRF attacks
Why this priority
- Public exploit reference
A fixed release or distro patch exists.
Risk facts
| CVSS score | 6.5 (Medium) |
| Attack vector | Network (remote) |
| Attack complexity | Low |
| Privileges needed | None |
| User interaction | Required |
| EPSS exploit chance | 0.5% (top 56%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-27 |
| 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-1843?
mailpress: upgrade to newer than 7.2.1. Exact commands for each OS are on this page.
Is CVE-2022-1843 being exploited?
CVE-2022-1843 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-1843 affect?
CVE-2022-1843 affects mailpress. Severity is medium (CVSS 6.5). The MailPress WordPress plugin through 7.2.1 does not have CSRF checks in various places, which could allow attackers to make a logged in admin change the settings, purge log files and more via CSRF attacks
How urgent is CVE-2022-1843?
Priority 39/100. Public exploit reference