CVE-2025-62523
BaseFortify
Publication date: 2025-10-27
Last updated on: 2025-11-04
Assigner: GitHub, Inc.
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| thm | pilos | to 4.8.0 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-942 | The product uses a web-client protection mechanism such as a Content Security Policy (CSP) or cross-domain policy file, but the policy includes untrusted domains with which the web client is allowed to communicate. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability is a Cross-Origin Resource Sharing (CORS) misconfiguration in PILOS before version 4.8.0. The middleware reflects the Origin request header back in the Access-Control-Allow-Origin response header without proper validation or a whitelist, while Access-Control-Allow-Credentials is set to true. This could allow a malicious website from a different origin to send requests, including credentials, to the PILOS API. However, Laravel's session handling adds origin checks that prevent cross-origin requests from being authenticated by default, so this vulnerability is not believed to be exploitable in typical PILOS deployments. The issue was fixed in version 4.8.0.
How can this vulnerability impact me? :
If exploitable, this vulnerability could allow a malicious website to perform actions or exfiltrate data using the victim's credentials by sending authenticated cross-origin requests to the PILOS API. However, due to Laravel's session-origin protections, such exploitation is unlikely in typical deployments unless other unknown vulnerabilities exist.
What immediate steps should I take to mitigate this vulnerability?
Upgrade PILOS to version 4.8.0 or later, where the CORS misconfiguration vulnerability has been patched.