Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure
Priority LOW 32CWE-200Published · Updated
Key facts
- Attack vector
- Network
- Privileges required
- None
- User interaction
- None
- Attack complexity
- Low
- Impact type
- Information disclosure
- Confidentiality · integrity · availability
- Low · None · None
- Fix status
- No fix listed
Attack profile from CVSS 3.1 · CNA. Fix status from CNA. Impact type from CWE-200.
Summary
The WordPress plugin Be POPIA Compliant exposed sensitive information to unauthenticated users consisting of site visitors emails and usernames via an API route, in versions up to an including 1.1.5.
Why it matters now
Exploitation None reported CISA SSVC · not in CISA KEV
EPSS 0.0117 67th percentileScored 2026-11-07
Fix No fix listed No fixed version in the sources yet
SSVC decision points
CISA ADP · SSVC 2.0.3
- Exploitation
- None
- Automatable
- Yes
- Technical impact
- Partial
The decision (Track, Attend, Act) also depends on your mission and well-being impact; see CISA's SSVC guide.
Affected products
| Vendor | Product | Affected versions | Fixed in | Status | Source |
|---|---|---|---|---|---|
| bepopiacompliant | Be POPIA Compliant | up to 1.1.5 | — | No fix listed | CNA |
- Be POPIA Compliant Vendorbepopiacompliant Affected up to 1.1.5 Fixed in — No fix listed CNA
Remediation
No fixed version listed by the sources yet.
Timeline
- 2026-10-02 Threatist record created from CVE-2022-1186
- 2026-10-03 Alias added: GHSA-9fwm-2jcf-cq55
References
Sources
- CVE-2022-1186 · CVE Program
- CVE-2022-1186 · NVD
- FIRST EPSS
- GHSA-9fwm-2jcf-cq55 · 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