LiveActive security incident?Get immediate response
CVE Record

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.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

CVE-2022-1186 is an unauthenticated information exposure in the WordPress plugin Be POPIA Compliant. Affected versions up to and including 1.1.5 could expose site visitor emails and usernames through an API route, creating privacy and compliance risk rather than direct system takeover.

Executive priority

Handle as a moderate privacy and compliance issue. It is not described as system compromise, but unauthenticated disclosure of visitor identifiers can create notification, trust, and regulatory exposure if the plugin was deployed on public sites.

Technical view

The issue is classified as CWE-200 with CVSS 3.1 score 5.3. Network access, low complexity, no privileges, and no user interaction are required. Impact is limited to confidentiality; the sources do not indicate integrity or availability impact.

Likely exposure

Exposure is limited to WordPress sites that installed Be POPIA Compliant versions up to and including 1.1.5. Sites without this plugin, or with versions not in the affected range, are not indicated as affected by the provided sources.

Exploitation context

The source bundle does not show CISA KEV listing or cite active exploitation. Because exploitation requires no authentication, exposed sites should still treat it as practical data exposure risk, especially where visitor email addresses are regulated or sensitive.

Researcher notes

The provided data identifies the affected plugin and version range but does not name the exact API route or fixed version. Avoid assuming active exploitation or a specific patch level beyond the cited Wordfence, CVE, and WordPress Trac references.

Mitigation direction

  • Inventory WordPress sites for the Be POPIA Compliant plugin.
  • Remove the plugin if it is unused or no longer needed.
  • Check vendor or WordPress plugin guidance for a fixed release.
  • Update beyond affected versions when a trusted fixed version is available.
  • Review privacy response obligations for exposed visitor emails and usernames.

Validation and detection

  • Confirm whether Be POPIA Compliant is installed on each WordPress site.
  • Record installed plugin versions and flag versions up to 1.1.5.
  • Review web logs for unauthenticated access to plugin API routes.
  • Check whether exposed data includes visitor emails or usernames.
  • Document findings for privacy, legal, and incident response teams.
Prepared
Confidence
medium
Sources
4

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-200: Information exposure and cloud metadata lookup

Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2022-1186 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
5.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
5.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

5.3Medium
CVSS 3.1 vector shape for CVE-2022-1186Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
bepopiacompliantBe POPIA Compliant0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-200 · source CWE mapping

Exposure of Sensitive Information to an Unauthorized Actor

Exposure of Sensitive Information to an Unauthorized Actor represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.