What this page helps you verify fast
This hub clusters every indexed record for Be POPIA Compliant so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
Review known vulnerability records for the WordPress plugin Be POPIA Compliant (`be-popia-compliant`), including severity, CVE references, affected versions, and patch status.
Recent tracked CVEs on this page include CVE-2022-47445 and CVE-2022-1186, so operators can jump from disclosure to patch validation without scanning the full feed first.
Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.
Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection
Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure
This hub clusters every indexed record for Be POPIA Compliant so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.
These recent records surface the CVE strings, patch cues, and direct report links most operators need first.
The Be POPIA Compliant plugin for WordPress is vulnerable to SQL Injection via the 'check_id' parameter in versions up to, and including, 1.2.0 due to insufficient escaping on the user suppl...
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 includi...
Sorted by latest disclosure date so newly published issues surface first.
The Be POPIA Compliant plugin for WordPress is vulnerable to SQL Injection via the 'check_id' parameter in versions up to, and including, 1.2.0 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on an existing SQL query. This makes it p...
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.