dbcve.org
Cross-Site Request Forgery (CSRF)Weakness · CWE-352

CVE-2025-48343

HIGH · 7.1 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
78/100
Remediation priority · High
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in Aaron Axelsen WPMU Ldap Authentication wpmuldap allows Stored XSS.This issue affects WPMU Ldap Authentication: from n/a through <= 5.0.1.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A CSRF vulnerability in the WPMU Ldap Authentication WordPress plugin (versions <= 5.0.1) allows authenticated administrators to unknowingly trigger requests that result in stored XSS. Attackers can craft malicious links or forms that, when opened by a logged-in administrator, cause the admin's browser to submit requests that store malicious scripts in the plugin's settings or user profile fields.

MitigationImplement anti-CSRF tokens (nonces) on all plugin admin forms and validate/sanitize all user-supplied input before storage and output. Update to the latest plugin version which should include CSRF protection and proper input sanitization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm the WPMU Ldap Authentication plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'WPMU Ldap Authentication' or 'LDAP Authentication' in the plugin list
    Affected if The plugin appears in the installed plugins list and is activated
  2. Identify the installed plugin version
    In the Plugins list, find the plugin and view the version number displayed beneath the plugin name. Alternatively, check the plugin's main PHP file for the 'Version' header in the plugin comment block
    Affected if The version is 5.0.1 or any version lower than 5.0.1
  3. Verify the plugin has admin configuration pages
    Look for LDAP-related menu items in the WordPress admin sidebar (typically under Settings, Users, or a dedicated LDAP menu). Access these pages to confirm the plugin exposes settings forms
    Affected if Admin settings pages exist and accept user input for LDAP configuration
  4. Test for CSRF protection on plugin forms
    Inspect the HTML source of the plugin's admin settings pages. Look for a hidden input field containing a nonce token (commonly named '_wpnonce', 'nonce', or similar) in all forms that modify settings
    Affected if Forms that save configuration settings lack a CSRF nonce token field or do not validate one on submission

If the plugin is active at version 5.0.1 or below AND contains admin settings forms without CSRF nonce protection, the environment is vulnerable to this CVE.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement anti-CSRF tokens (nonces) on all plugin admin forms and validate/sanitize all user-supplied input before storage and output. Update to the latest plugin version which should include CSRF protection and proper input sanitization.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA1.0 h
12.0 hours of engineering $2,110
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-48343 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-48343 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data