WPMU Ldap Authentication <= 5.0.1 - Cross-Site Request Forgery to Stored Cross-Site Scripting
Strategic Overview
- Status
- Patched in 5.1
- Affected Plugin
- WPMU Ldap Authentication
- Affected Version
<= 5.0.1- CVSS
- 6.1Medium
- Weakness type
- CWE-352 · Cross-Site Request Forgery (CSRF)
- CVE
CVE-2025-48343
At a glance
CVE-2025-48343 is a medium-severity Cross-Site Request Forgery (CSRF) vulnerability in the WPMU Ldap Authentication WordPress plugin, affecting versions <= 5.0.1. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 5.1; sites on affected versions should update now. Disclosed August 2025, reported by Nguyen Xuan Chien.
Vulnerability Overview
The WPMU Ldap Authentication plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 5.0.1. This is due to missing or incorrect nonce validation on a function. This makes it possible for unauthenticated attackers to update settings and inject malicious web scripts via a forged request granted they can trick a site administrator into performing an action such as clicking on a link.
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.
CWE-352: Cross-Site Request Forgery (CSRF)
Reaching this weakness in WPMU Ldap Authentication <= 5.0.1 takes a caller who can reach the endpoint. Cross-site request forgery abuses the fact that browsers attach a victim's cookies to any request, so a state-changing action that only checks who you are, not whether you meant to act, can be triggered from another site.
An attacker who gets a logged-in user to load a crafted page can perform that action as them, with the impact scaling to whatever the victim's role is allowed to do. For WPMU Ldap Authentication the fix is 5.1: builds <= 5.0.1 are affected, anything from 5.1 onward is not.
Remediation
Update to version 5.1, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to WPMU Ldap Authentication: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: WPMU Ldap Authentication 5.1 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C