dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2025-13910

MEDIUM · 6.1 CVSS v3.1 Published 2026-03-21
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
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
The WP-WebAuthn plugin for WordPress is vulnerable to Unauthenticated Stored Cross-Site Scripting via the `wwa_auth` AJAX endpoint in all versions up to, and including, 1.3.4 due to insufficient input sanitization and output escaping on user supplied attributes logged by the plugin. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses the plugin's log page, provided that the logging option is enabled in the plugin settings.

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

The WP-WebAuthn plugin versions up to 1.3.4 have a stored XSS vulnerability in the wwa_auth AJAX endpoint. Unauthenticated attackers can inject malicious scripts through user-supplied attributes that get logged (when logging is enabled). These scripts execute when administrators view the plugin's log page due to insufficient input sanitization and output escaping.

MitigationUpdate the WP-WebAuthn plugin to version 1.3.5 or later. If unable to update, disable the logging option in plugin settings as a temporary mitigation until the plugin can be updated.

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
None

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

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 WP-WebAuthn plugin installation and version
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, locate WP-WebAuthn, and note the version number displayed. Alternatively, check the plugin header in wp-content/plugins/wp-webauthn/wp-webauthn.php for the 'Version' field.
    Affected if The installed version is 1.3.4 or lower (any version up to and including 1.3.4).
  2. Verify logging is enabled
    Go to WordPress admin > WebAuthn settings (or plugin settings page) and locate the logging option. Check whether logging is turned on or off. This setting may also be stored in the wp_options table under option_name containing 'webauthn' and 'log'.
    Affected if Logging is enabled - the XSS payload executes only when administrators view the plugin's log page, so logging must be active for the attack chain to complete.
  3. Check for the wwa_auth AJAX endpoint
    Verify the plugin AJAX handler exists by checking if the file wp-content/plugins/wp-webauthn/includes/class-ajax.php or similar contains 'wwa_auth' and is loaded. You can also attempt a curl request to admin-ajax.php with action=wwa_auth (though this requires understanding the endpoint parameters).
    Affected if The wwa_auth AJAX endpoint is present and accessible - this is the injection point for the stored XSS.
  4. Inspect plugin logs for suspicious script tags
    If logging is enabled, access the plugin's log viewing page (typically under WebAuthn settings or a dedicated Logs section in the plugin admin menu). Look for any log entries containing <script> tags, javascript:, or other HTML/script injection patterns in user-supplied fields.
    Affected if Log entries contain unsanitized HTML or script tags that would execute when viewed - this confirms active exploitation.

You are affected if WP-WebAuthn version 1.3.4 or lower is installed AND the logging feature is enabled, allowing injected scripts to execute when you view the plugin logs.

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.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the WP-WebAuthn plugin to version 1.3.5 or later. If unable to update, disable the logging option in plugin settings as a temporary mitigation until the plugin can be updated.

Recommended fix Moderate confidence

WP-WebAuthn version 1.3.5

  1. Upgrade the WP-WebAuthn plugin to version 1.3.5 or later
  2. After upgrading, verify that the plugin functions correctly and the logging feature works as expected
  3. Check plugin settings to ensure logging is configured appropriately for your security requirements

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13910 — 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-13910 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