VulnTitan VulnTitan Security command center
Plugin Vulnerability Hub
Plugin 2 known issues Latest disclosed Mar 15, 2023

Be POPIA Compliant Vulnerabilities

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.

View on WordPress.org Back to Feed
Known Records
2
High or Critical
0
Patch Coverage
100%
Last Updated
Jan 31, 2025
Related Security Guides

Use these guides while reviewing Be POPIA Compliant fixes

Pair this plugin vulnerability hub with practical WordPress hardening, scanner, and patch workflow guidance.

Hardening
WordPress hardening checklist for exposed plugins

Review patch cadence, privileged access, XML-RPC exposure, backups, and monitoring controls.
Plugin Security
WordPress plugin security basics for patch decisions

Use ownership, update testing, least privilege, and removal criteria to reduce plugin risk.
Scanning
WordPress vulnerability scanner buyer's guide

Compare scanner coverage for plugin CVEs, version detection, alert noise, and remediation workflow.
Patch Decision Workflow

How to prioritize Be POPIA Compliant remediation

Use the hub as a decision layer before opening individual records: confirm whether the issue has a CVE, whether a fixed version exists, and whether the affected range overlaps production installs.

Search-Ready Records
1
1. Match the Package
Confirm the installed WordPress plugin slug is be-popia-compliant before acting on any CVE from this cluster.
2. Sort by Severity
Start with 0 high or critical records, then review medium and unrated findings with public references.
3. Check Patch Evidence
2 records include a patch path; verify compatibility before closing the finding.
4. Monitor Gaps
0 records still lack a listed fixed release, so keep this hub in the review queue.
High-Signal Remediation Targets
CVE-2022-47445 Medium
SQL Injection remediation for Be POPIA Compliant

Affected range: Versions up to 1.2.0. Fixed version: 1.3.0.

CVE-2022-1186 Medium
Sensitive Information Exposure remediation for Be POPIA Compliant

Affected range: Versions up to 1.1.5. Fixed version: 1.1.16.

Priority CVE Quick Links

Fast paths into Be POPIA Compliant CVE reports

Start with the highest-signal CVE records for this WordPress plugin before scanning the full vulnerability feed.

Indexed CVEs
2
Tracked CVE Issue Type Affected Versions Fixed Version CVSS
CVE-2022-47445
Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection
 SQL Injection Versions up to 1.2.0 1.3.0 CVSS 6.5
CVE-2022-1186
Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure
 Sensitive Information Exposure Versions up to 1.1.5 1.1.16 CVSS 5.3
CVE-2022-47445 Medium 1.3.0
CVE-2022-47445 Be POPIA Compliant SQL Injection

Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection

CVE-2022-1186 Medium 1.1.16
CVE-2022-1186 Be POPIA Compliant Sensitive Information Exposure

Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure

Coverage Snapshot

What this page helps you verify fast

This hub clusters tracked records for Be POPIA Compliant so operators can confirm whether a disclosed issue maps to the installed slug, version range, and patch path.

Patch Visibility
2 records include a published patch path, leaving 0 with no listed safe release yet.
Severity Mix
0 critical and 0 high severity findings.
Recent CVEs
CVE-2022-47445 and CVE-2022-1186
Reference Workflow
Jump from the hub into the full report when you need remediation notes, exploit context, CVSS vectors, or source references.
Triage First

Open the records most likely to drive action

These recent records surface the CVE strings, patch cues, and direct report links most operators need first.

Known Vulnerabilities

Reports for Be POPIA Compliant

Sorted by latest disclosure date so newly published issues surface first.

Plugin Medium Patched: Yes CVE-2022-47445
CVE-2022-47445: Be POPIA Compliant <= 1.2.0 - Authenticated (Subscriber+) SQL Injection

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...

Published
Mar 15, 2023
Patched Release
1.3.0
Affected Versions
Versions up to 1.2.0
Next Step
Update to 1.3.0 or newer if supported.
Review CVE-2022-47445 fixed version details Open CVE Reference
Plugin Medium Patched: Yes CVE-2022-1186
CVE-2022-1186: Be POPIA Compliant <= 1.1.5 - Sensitive Information Exposure

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.

Published
Mar 30, 2022
Patched Release
1.1.16
Affected Versions
Versions up to 1.1.5
Next Step
Update to 1.1.16 or newer if supported.
Review CVE-2022-1186 fixed version details Open CVE Reference