LiveActive security incident?Get immediate response
CVE Record

CVE-2022-41839: WordPress LoginPress plugin <= 1.6.2 - Broken Access Control vulnerability

Broken Access Control vulnerability in WordPress LoginPress plugin <= 1.6.2 on WordPress leading to unauth. changing of Opt-In or Opt-Out tracking settings.

MediumCVSS 5.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

This issue lets unauthenticated internet users change LoginPress tracking opt-in or opt-out settings on vulnerable WordPress sites. It is not described as data theft or site takeover, but it is still an integrity failure in an admin-facing plugin setting and should be removed from production exposure through normal plugin governance.

Executive priority

Treat this as a moderate-priority hygiene issue. It does not indicate compromise or sensitive data exposure from the available sources, but unauthenticated setting changes on public WordPress sites are unacceptable and should be closed during the next routine patch cycle.

Technical view

CVE-2022-41839 is a broken access control flaw in WPBrigade LoginPress | Custom Login Page Customizer versions 1.6.2 and earlier. The CVSS 3.1 vector is AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N, reflecting unauthenticated network access with low integrity impact only.

Likely exposure

Exposure is limited to WordPress sites with LoginPress installed at version 1.6.2 or earlier. The source bundle does not identify affected CPEs or hosted-service variants. Public WordPress login pages increase discoverability, but the documented impact is confined to tracking preference settings.

Exploitation context

The CVE is not listed as KEV in the bundle, and no cited source states active exploitation. The vulnerability requires no authentication or user interaction, which lowers the effort required if a vulnerable site is reachable, but the documented business impact is limited.

Researcher notes

Available evidence identifies the affected component, version range, impact, and CVSS vector, but not a specific fixed version or detailed root cause. Avoid expanding impact beyond unauthorized modification of LoginPress tracking settings unless vendor analysis provides more detail.

Mitigation direction

  • Inventory WordPress sites for LoginPress installations and versions.
  • Prioritize updating or replacing LoginPress versions 1.6.2 and earlier.
  • Check WPBrigade or Patchstack guidance for the fixed release and supported remediation.
  • Review whether tracking settings changed unexpectedly on affected sites.
  • Remove unused LoginPress installations from production WordPress sites.

Validation and detection

  • Confirm each WordPress site's installed LoginPress version.
  • Verify no production site runs LoginPress 1.6.2 or earlier.
  • Review administrative logs or settings history for unexpected tracking preference changes.
  • Document remediation status in the vulnerability management system.
  • Recheck exposed WordPress assets after plugin updates or removals.
Prepared
Confidence
high
Sources
3

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 · low confidence lookup

CWE-264: Exact CWE lookup

Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. 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-41839 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:N/I:L/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
2Source 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:N/I:L/A:N3.91.4Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

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

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/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
WPBrigadeLoginPress | Custom Login Page Customizer (WordPress plugin)<= 1.6.2Listed
Weakness

CWE details

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

CWE-264 · source CWE mapping

Permissions, Privileges, and Access Controls

Permissions, Privileges, and Access Controls represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.