{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-13910 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-13910 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-13910 is a medium-severity cross-site scripting vulnerability in axton WP-WebAuthn, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-13910 and fix it if it is affected.\n\nWhat it is: CVE-2025-13910 is a medium-severity cross-site scripting vulnerability in axton WP-WebAuthn, published on 21 Mar 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-13910 in the wild and no public exploit code.\n\nAffected product: axton WP-WebAuthn. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-13910/ (Markdown: https://insights.sbomify.com/CVE-2025-13910/index.md)","id":"CVE-2025-13910","markdown":"https://insights.sbomify.com/CVE-2025-13910/index.md","name":"CVE-2025-13910","record":{"aliases":["GHSA-66vw-3ggr-5vvg"],"analysis":{"component_type":"cms_plugin","fix_type":"upgrade","impacts":["code_execution"],"network_reachable":"yes","non_default_config":true,"product_category":"WordPress plugin","requires_auth":"none","summary":"Unauthenticated attackers can inject arbitrary scripts into the WP-WebAuthn log page if logging is enabled, leading to stored XSS execution.","user_interaction":"required","vuln_class":"xss"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"Wordfence","cpe":[],"cvss":{"score":6.1,"severity":"medium","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N","version":"3.1"},"cwes":[{"id":"CWE-79","name":"Improper Neutralization of Input During Web Page Generation"}],"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.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"WP-WebAuthn \u003c= 1.3.4 - Unauthenticated Stored Cross-Site Scripting","id":"CVE-2025-13910","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"xss","year":"2025"},"n_packages":0,"n_references":4,"next":{"headline":"Inductive Automation Ignition Execution with Unnecessary Privileges","id":"CVE-2025-13911"},"packages":[],"prev":{"headline":"Information Disclosure via Multi-Tenant Authentication Flows in WSO2 Identity Server Allows Cross-Tenant PII Exposure","id":"CVE-2025-13909"},"products":["WP-WebAuthn"],"published":"2026-03-21","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"partial"},"state":"PUBLISHED","updated":"2026-04-08","vendors":["axton"]},"summary":"Unauthenticated attackers can inject arbitrary scripts into the WP-WebAuthn log page if logging is enabled, leading to stored XSS execution.","url":"https://insights.sbomify.com/CVE-2025-13910/"}