CVE-2025-13910
Received Received - Intake
Stored XSS in WP-WebAuthn Plugin via Unauthenticated AJAX Endpoint

Publication date: 2026-03-21

Last updated on: 2026-03-21

Assigner: Wordfence

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-21
Last Modified
2026-03-21
Generated
2026-06-16
AI Q&A
2026-03-21
EPSS Evaluated
2026-06-15
NVD
CVE-2025-13910
EUVD
EUVD-2025-208914
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
webauthn wp_webauthn to 1.3.4 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Quick Actions
Instant insights powered by AI
Executive Summary

The WP-WebAuthn plugin for WordPress has a vulnerability called Unauthenticated Stored Cross-Site Scripting (XSS) in versions up to and including 1.3.4. This occurs because the plugin does not properly sanitize or escape user-supplied input in the wwa_auth AJAX endpoint. As a result, an attacker who is not logged in can inject malicious scripts into the plugin's log page if logging is enabled.

These injected scripts will execute whenever any user accesses the plugin's log page, potentially compromising their security.

Impact Analysis

This vulnerability can allow unauthenticated attackers to execute arbitrary scripts in the context of users who view the plugin's log page. This can lead to theft of sensitive information, session hijacking, or other malicious actions performed on behalf of the affected users.

Since the attack requires the logging option to be enabled and users to visit the log page, the impact depends on the plugin's configuration and user behavior.

Compliance Impact

I don't know

Detection Guidance

I don't know

Mitigation Strategies

I don't know

Chat Assistant
Ask questions about this CVE
Hi! I’m here to help you understand CVE-2025-13910. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70
EPSS Chart