CVE-2022-1832: 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

medium Affects capa-protect (WordPress plugin). Feed 2026.10.29.4, updated 2026-10-29; published ; advisory modified .

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

Package
capa-protect (WordPress plugin) WordPress
Affected versions
<=0.5.8.2
Fixed in
no fix recorded
Severity
medium  CVSS 6.5
Exploitation
not on CISA KEV · EPSS 1% (45.0th percentile)
Published
2022-06-20
Source
nvd

References

CWE-352
NVD recordcapa-protect (WordPress plugin) advisories

Am I affected?

Find out in one command. phpwarden checks your WordPress install against this advisory and 20,000+ others, ranked by real-world exploitation (CISA KEV + EPSS). Free, offline, open data.

# PHP projects (recommended)
composer require --dev phpwarden/phpwarden
# then
vendor/bin/phpwarden wordpress /var/www/html

# or, without Composer
pipx install phpwarden   &&   phpwarden wordpress /var/www/html

Or keep it checked automatically with the GitHub Action or a nightly cron; see WordPress docs.

Install docs   How findings are ranked

Related advisories