HomeWordPress vulnerabilitiesWP-WebAuthn
WP-WebAuthn vulnerabilities
WP-WebAuthn has 2 known vulnerabilities in this database. The most recent published record is dated 21 Mar 2026.
- Known vulnerabilities
- 2
- Active installs
- 2,000+
- Latest version
- 1.4.1
- Last updated
- 15 Apr 2026
- Most recent
- 21 Mar 2026
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Cross-site scripting (XSS) CVE-2025-13910 | Medium 6.1 | Up to 1.3.4 | Fixed in a later version (latest 1.4.1) | 21 Mar 2026 |
| Cross-site scripting (XSS) CVE-2024-9023 | Medium 6.4 | Up to 1.3.1 | Fixed in a later version (latest 1.4.1) | 28 Sep 2024 |
Read the published descriptions
- CVE-2025-13910, 21 Mar 2026
- 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. CVE record
- CVE-2024-9023, 28 Sep 2024
- The WP-WebAuthn plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the plugin's wwa_login_form shortcode in all versions up to, and including, 1.3.3 due to insufficient input sanitization and output escaping on user supplied attributes. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. CVE record
What to do if you run WP-WebAuthn
If you run WP-WebAuthn, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new WP-WebAuthn vulnerabilities
Free. We email you when a new vulnerability is published for WP-WebAuthn, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.