Session-backed API access via reflected CORS origins
Published Feb 6, 2025 · Updated Feb 12, 2025
Permissive CORS in Mindskip XZS MySQL 3.9.0 allows remote attackers to make credentialed cross-origin API requests from untrusted sites. The CORS handler reflects an attacker-controlled Origin into Access-Control-Allow-Origin while also returning Access-Control-Allow-Credentials as true. Exploitation requires an authenticated user to interact with attacker-controlled web content, exposing session-backed data reads or unauthorized API actions.
Summary
What happened
Permissive CORS in Mindskip XZS MySQL 3.9.0 allows remote attackers to make credentialed cross-origin API requests from untrusted sites. The CORS handler reflects an attacker-controlled Origin into Access-Control-Allow-Origin while also returning Access-Control-Allow-Credentials as true. Exploitation requires an authenticated user to interact with attacker-controlled web content, exposing session-backed data reads or unauthorized API actions.
The record
- CVE
- CVE-2025-1083
- Published
- Feb 6, 2025
- Updated
- Feb 12, 2025
- Vendor
- Mindskip
- Product
- XZS MySQL
- Classifications
- CWE-942, CWE-346
- Attack vector
- network
- Privileges
- unauthenticated
Timeline
How it unfolded
- Feb 6, 2025CVE publishedPublication date reported by the CVE source.
- Feb 12, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.9.0
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- Credentialed arbitrary-Origin CORS request proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo