CaPa Protect <= 0.5.8.2 - Arbitrary Settings Update via CSRF
Priority LOW 30CWE-352Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- Required
- Attack complexity
- Low
- Impact type
- Tampering
- Confidentiality · integrity · availability
- None · High · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · NVD. Fix status from CNA. Impact type from CWE-352.
Summary
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 it matters now
EPSS 0.00534 45th percentileScored 2026-11-07
Public exploit Yes 1 exploit referenceTagged by NVD
Fix No fix listed No fixed version in the sources yet
SSVC decision points
Not available: CISA has not published SSVC decision points for this record.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| Unknown | CaPa Protect | 0.5.8.2 – 0.5.8.2 | — | No fix listed | CNA |
- CaPa Protect VendorUnknown Affected 0.5.8.2 – 0.5.8.2 Fixed in — No fix listed CNA
CPE configurations NVD · 1
| CPE | Versions | Role | Vendor |
|---|---|---|---|
| cpe:2.3:a:capa_protect_project:capa_protect:*:*:*:*:*:wordpress:*:* | up to 0.5.8.2 | Vulnerable | Capa Protect Project |
- cpe:2.3:a:capa_protect_project:capa_protect:*:*:*:*:*:wordpress:*:* Versions up to 0.5.8.2 Vulnerable ·Capa Protect Project
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2022-1832
- 2026-10-03 Alias added: GHSA-fj6q-3p3v-wc7h
References
Sources
- CVE-2022-1832 · CVE Program
- CVE-2022-1832 · NVD
- FIRST EPSS
- GHSA-fj6q-3p3v-wc7h · GitHub Advisory Database · CC BY 4.0
This product uses the NVD API but is not endorsed or certified by the NVD. Sources and licences