PatchTheCVECVE-2022-1832: The CaPa Protect WordPress plugin through 0.5.8.2 does not have CSRF check in place when updating its settings
CVE-2022-1832 is a medium-severity flaw (CVSS 6.5) affecting capa protect. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.
The CaPa Protect WordPress plugin through 0.5.8.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack and disable the applied protection.
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 55%) |
| CISA exploited list | No |
| Weakness | CWE-352 |
| Published | 2022-06-20 |
| 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-1832?
capa protect: upgrade to newer than 0.5.8.2. Exact commands for each OS are on this page.
Is CVE-2022-1832 being exploited?
CVE-2022-1832 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-1832 affect?
CVE-2022-1832 affects capa protect. Severity is medium (CVSS 6.5). The CaPa Protect WordPress plugin through 0.5.8.2 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack and disable the applied protection.
How urgent is CVE-2022-1832?
Priority 39/100. Public exploit reference