Ldap WP Login / Active Directory Integration <= 3.0.1 - Missing Authorization
Strategic Overview
- Status
- Patched in 3.0.2
- Affected Plugin
- Ldap WP Login / Active Directory Integration
- Affected Version
< 3.0.2- CVSS
- 7.3High
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2022-2987
At a glance
CVE-2022-2987 is a high-severity Missing Authorization vulnerability in the Ldap WP Login / Active Directory Integration WordPress plugin, affecting versions < 3.0.2. It carries a CVSS score of 7.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 3.0.2; sites on affected versions should update now. Disclosed September 2022, reported by István Márton.
Vulnerability Overview
The Ldap WP Login / Active Directory Integration plugin for WordPress is vulnerable to authorization bypass and Cross-Site Request Forgery in versions up to, and including 3.0.1, due to missing nonce and capability checks on several of it's functions called via init hooks. This makes it possible for unauthenticated attackers to update the plugin's setting and potentially connect their own LDAP server to make authentication bypass possible.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user.
CWE-862: Missing Authorization
Reaching this weakness in Ldap WP Login / Active Directory Integration < 3.0.2 takes a caller who can reach the endpoint. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For Ldap WP Login / Active Directory Integration the fix is 3.0.2: builds < 3.0.2 are affected, anything from 3.0.2 onward is not.
Remediation
Update to version 3.0.2, or a newer patched version
How does WordSec protect against this?
Because it turns on account access, WordSec's login security is the relevant layer: role-based two-factor, captcha and brute-force limits raise the cost of getting the account this needs. None of that substitutes for the fix: Ldap WP Login / Active Directory Integration 3.0.2 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C