Be POPIA Compliant [be-popia-compliant] < 1.3.0
unknown
[en] Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in Web-X Be POPIA Compliant be-popia-compliant allows SQL Injection.This issue affects Be POPIA Compliant: from n/a through 1.2.0.
- Affected:
- up to 1.3.0
- Fixed in:
- 1.3.0
- Disclosed:
- Nov 3, 2023
CVE-2022-47445 on NVD →
Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection
medium
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 possible for authenticated attackers, wi...
- CVSS:
- 6.5
- Affected:
- up to 1.2.0
- Fixed in:
- 1.3.0
- Disclosed:
- Mar 15, 2023
CVE-2022-47445 on NVD →
Be POPIA Compliant [be-popia-compliant] < 1.1.16
unknown
[en] 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.
- Affected:
- up to 1.1.16
- Fixed in:
- 1.1.16
- Disclosed:
- Apr 19, 2022
CVE-2022-1186 on NVD →
Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure
medium
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.
- CVSS:
- 5.3
- Affected:
- up to 1.1.5
- Fixed in:
- 1.1.16
- Disclosed:
- Mar 30, 2022
CVE-2022-1186 on NVD →
Protect your WordPress site
Run a free security scan to detect vulnerable plugins and themes, exposed files, and malware — no plugin install, no signup.
Scan your site free
← Back to the vulnerability database