WordPress plugin
Be POPIA Compliant security & vulnerabilities
No known unpatched vulnerabilities in the latest version
All 2 known vulnerabilities are fixed in the latest release. If you run an older version, update to null or newer.
- Critical0
- High0
- Medium2
- Low0
All Be POPIA Compliant vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| Medium6.5 | Authenticated (Subscriber+) SQL Injection ≤1.2.0Update to 1.3.0 | CVE-2022-47445 | |
| Medium5.3 | Sensitive Information Exposure ≤1.1.5Update to 1.1.16 | CVE-2022-1186 |
- Medium6.5Authenticated (Subscriber+) SQL Injection
≤1.2.0Update to 1.3.0
- Medium5.3Sensitive Information Exposure
≤1.1.5Update to 1.1.16
Be POPIA Compliant: common questions
Does Be POPIA Compliant have known vulnerabilities?
Yes. VulnCrest Radar lists 2 known vulnerabilities in Be POPIA Compliant: 2 medium. None are known to affect version null.
How do I check which version of Be POPIA Compliant I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent Be POPIA Compliant vulnerability?
CVE-2022-47445, published Mar 15, 2023: Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection. Severity: Medium (CVSS 6.5).
Is any Be POPIA Compliant vulnerability listed in CISA KEV?
No. None of the known Be POPIA Compliant vulnerabilities is currently listed in the CISA KEV catalog.