CVE-2025-13910
Stored XSS in WP-WebAuthn Plugin via Unauthenticated AJAX Endpoint
Publication date: 2026-03-21
Last updated on: 2026-03-21
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| webauthn | wp_webauthn | to 1.3.4 (inc) |
Helpful Resources
Exploitability
| 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 Powered Q&A
Can you explain this vulnerability to me?
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.
How can this vulnerability impact me? :
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.
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
I don't know
How can this vulnerability be detected on my network or system? Can you suggest some commands?
I don't know
What immediate steps should I take to mitigate this vulnerability?
I don't know