CVE-2025-50864: n/a
An Origin Validation Error in the elysia-cors library thru 1.3.0 allows attackers to bypass Cross-Origin Resource Sharing (CORS) restrictions. The library incorrectly validates the supplied origin by checking if it is a substring of any domain in the site's CORS policy, rather than performing an exact match. For example, a malicious origin like "notexample.com", "example.common.net" is whitelisted when the site's CORS policy specifies "example.com." This vulnerability enables unauthorized access to user data on sites using the elysia-cors library for CORS validation.
AI Analysis
Technical Summary
The elysia-cors library through version 1.3.0 suffers from an origin validation error where the supplied origin is checked as a substring of allowed domains instead of an exact match. This flaw allows malicious origins such as "notexample.com" or "example.common.net" to be incorrectly accepted when the policy specifies "example.com." As a result, attackers can bypass CORS restrictions and potentially access user data on sites using this library for CORS validation. The vulnerability is tracked as CVE-2025-50864 and is associated with CWE-178 (Improper Neutralization of Argument Delimiters in a Command).
Potential Impact
This vulnerability enables attackers to bypass Cross-Origin Resource Sharing (CORS) policies, potentially allowing unauthorized websites to access sensitive user data from affected sites. While it does not impact confidentiality directly via network access, it compromises the integrity of CORS enforcement, increasing the risk of data exposure through unauthorized cross-origin requests.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing strict origin validation outside of the elysia-cors library or avoid using affected versions (<=1.3.0).
CVE-2025-50864: n/a
Description
An Origin Validation Error in the elysia-cors library thru 1.3.0 allows attackers to bypass Cross-Origin Resource Sharing (CORS) restrictions. The library incorrectly validates the supplied origin by checking if it is a substring of any domain in the site's CORS policy, rather than performing an exact match. For example, a malicious origin like "notexample.com", "example.common.net" is whitelisted when the site's CORS policy specifies "example.com." This vulnerability enables unauthorized access to user data on sites using the elysia-cors library for CORS validation.
CVSS v3.1
Score 6.5medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The elysia-cors library through version 1.3.0 suffers from an origin validation error where the supplied origin is checked as a substring of allowed domains instead of an exact match. This flaw allows malicious origins such as "notexample.com" or "example.common.net" to be incorrectly accepted when the policy specifies "example.com." As a result, attackers can bypass CORS restrictions and potentially access user data on sites using this library for CORS validation. The vulnerability is tracked as CVE-2025-50864 and is associated with CWE-178 (Improper Neutralization of Argument Delimiters in a Command).
Potential Impact
This vulnerability enables attackers to bypass Cross-Origin Resource Sharing (CORS) policies, potentially allowing unauthorized websites to access sensitive user data from affected sites. While it does not impact confidentiality directly via network access, it compromises the integrity of CORS enforcement, increasing the risk of data exposure through unauthorized cross-origin requests.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, users should consider implementing strict origin validation outside of the elysia-cors library or avoid using affected versions (<=1.3.0).
Technical Details
- Data Version
- 5.1
- Assigner Short Name
- mitre
- Date Reserved
- 2025-06-16T00:00:00.000Z
- State
- PUBLISHED
Threat ID: 68a5e397ad5a09ad0005f17f
Added to database: 08/20/2025, 15:02:47 UTC
Last enriched: 07/05/2026, 21:24:44 UTC
Last updated: 09/10/2026, 19:36:50 UTC
Views: 163
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.