Security readout for executives and security teams
Plain-English summary
This WordPress LDAP login plugin allowed unauthenticated outsiders to change authentication settings before version 3.0.2. An attacker could redirect LDAP authentication to a server they control, potentially bypassing normal login controls. The issue affects integrity of access decisions rather than data confidentiality or availability in the CVSS record.
Executive priority
Prioritize remediation for any public WordPress site using this plugin for business authentication. The vulnerability can undermine login trust without attacker credentials, making it a high-priority identity control issue even without confirmed active exploitation evidence.
Technical view
CVE-2022-2987 is a missing authorization and CSRF-control flaw in settings update logic hooked to WordPress init. For Ldap WP Login / Active Directory Integration before 3.0.2, unauthenticated requests could modify LDAP settings. CVSS 3.1 is 7.5: network, low complexity, no privileges, no user interaction, high integrity impact.
Likely exposure
Exposure is likely limited to WordPress sites running the Ldap WP Login / Active Directory Integration plugin before 3.0.2, especially public sites using LDAP or Active Directory authentication. The bundle does not identify affected CPEs or vendor ownership beyond the plugin name.
Exploitation context
The provided sources support unauthenticated remote settings modification and authentication bypass potential. CISA KEV is false, and the bundle provides no cited evidence of active exploitation. Treat internet-facing WordPress authentication plugins as sensitive because compromise can affect administrative access.
Researcher notes
The core issue combines missing authorization with missing CSRF checks on settings updates. The security consequence is integrity compromise of LDAP authentication configuration. The source bundle is limited; it does not include detailed patch diff, exploit availability, affected CPEs, or operational indicators.
Mitigation direction
- Update Ldap WP Login / Active Directory Integration to 3.0.2 or later if available.
- Review vendor or WordPress plugin guidance for any additional remediation steps.
- Restrict administrative WordPress access paths where operationally feasible.
- Audit LDAP plugin settings for unexpected server, bind, or authentication changes.
- Rotate credentials if logs or settings suggest unauthorized authentication changes.
Validation and detection
- Inventory WordPress sites for this plugin and record installed versions.
- Confirm no active installation is below version 3.0.2.
- Review current LDAP server settings against approved configuration records.
- Check WordPress and web logs for unexpected settings-update activity around authentication paths.
- Verify administrative users and recent logins are expected.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
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-352: User-session and phishing behavior lookup
Client-side and session-facing weaknesses should be reviewed alongside initial-access and user-execution behaviors. 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 lookupCWE-862: Authorization and privilege behavior lookup
Authorization weaknesses can support privilege escalation and valid-account review, depending on exploit path. 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 lookupCVE-2022-2987 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- High
- CVSS
- 7.5 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
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.
CVSS vector scores
1 official scoreWe 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.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N3.93.6Primary CVE scoreVulnerability scoring details
Base CVSS 3.1 score
7.5HighVector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N
Source materials
- CVE List V5 sourceCVE List V5
- https://wpscan.com/vulnerability/0d9638b9-bf8a-474f-992d-2618884d3f67CVE reference · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Cross-Site Request Forgery (CSRF)
Cross-Site Request Forgery (CSRF) represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Missing Authorization
Missing Authorization represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.