Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-30964: CWE-346: Origin Validation Error in web-auth webauthn-framework

0
Medium
VulnerabilityCVE-2026-30964cvecve-2026-30964cwe-346
Published: Tue Mar 10 2026 (03/10/2026, 17:16:46 UTC)
Source: CVE Database V5
Vendor/Project: web-auth
Product: webauthn-framework

Description

web-auth/webauthn-lib is an open source set of PHP libraries and a Symfony bundle to allow developers to integrate that authentication mechanism into their web applications. Prior to 5.2.4, when allowed_origins is configured, CheckAllowedOrigins reduces URL-like values to their host component and accepts on host match alone. This makes exact origin policies impossible to express: scheme and port differences are silently ignored. This vulnerability is fixed in 5.2.4.

AI-Powered Analysis

AILast updated: 03/10/2026, 18:09:09 UTC

Technical Analysis

The web-auth webauthn-framework is a PHP library and Symfony bundle that facilitates integration of WebAuthn authentication into web applications. Prior to version 5.2.4, when the allowed_origins configuration was set, the framework's CheckAllowedOrigins function performed origin validation by reducing URL-like values to their host component only. This means that the scheme (e.g., http vs https) and port number were ignored during origin checks. As a result, the origin validation was incomplete and allowed origin policies could not be precisely enforced. An attacker could exploit this by crafting requests from origins that share the same host but differ in scheme or port, bypassing origin restrictions. This vulnerability is classified under CWE-346 (Origin Validation Error). The CVSS 3.1 base score is 5.4 (medium severity), reflecting that the vulnerability is remotely exploitable without privileges but requires user interaction and results in limited confidentiality and integrity impact without affecting availability. The flaw could lead to unauthorized authentication or cross-origin request forgery scenarios, undermining the security guarantees of WebAuthn implementations relying on this library. The issue was addressed in version 5.2.4 by enforcing exact origin matching that includes scheme and port, restoring strict origin policy enforcement.

Potential Impact

The vulnerability undermines the origin validation mechanism critical to WebAuthn authentication flows, potentially allowing attackers to bypass origin restrictions. This can lead to unauthorized authentication attempts, session hijacking, or cross-origin attacks that compromise user credentials or session integrity. Organizations using vulnerable versions of the webauthn-framework may face increased risk of account takeover or impersonation attacks. The impact is primarily on confidentiality and integrity of authentication processes, with no direct availability impact. Because WebAuthn is increasingly adopted for strong passwordless authentication, exploitation could erode trust in authentication security and expose sensitive user accounts. The vulnerability affects any web application integrating the vulnerable library versions, especially those exposed to untrusted networks or users. While no known exploits are reported, the ease of exploitation due to lack of required privileges and remote accessibility makes timely remediation important to prevent potential attacks.

Mitigation Recommendations

Organizations should upgrade the web-auth webauthn-framework to version 5.2.4 or later, where the origin validation logic correctly enforces exact origin matching including scheme and port. Until upgrade is possible, developers should implement additional server-side origin checks that verify the full origin string rather than just the host component. Security teams should audit their WebAuthn implementations to confirm they do not rely solely on host-based origin validation. Web application firewalls (WAFs) can be configured to detect and block suspicious cross-origin requests that do not match expected schemes and ports. Monitoring authentication logs for unusual origin patterns or failed authentication attempts from unexpected origins can help detect exploitation attempts. Educating developers about the importance of strict origin validation in WebAuthn flows is also recommended to prevent similar issues.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-03-07T17:53:48.814Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 69b05633ea502d3aa87d6b87

Added to database: 3/10/2026, 5:34:43 PM

Last enriched: 3/10/2026, 6:09:09 PM

Last updated: 3/14/2026, 12:01:21 AM

Views: 31

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console in Console -> Billing for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses