Lichess lila 2025-06-02 Game Export API players server-side request forgery
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 0.00 |
Summary
A vulnerability classified as critical has been found in Lichess lila 2025-06-02. This affects an unknown function of the component Game Export API. Performing a manipulation of the argument players results in server-side request forgery. This vulnerability was named CVE-2025-52186. The attack may be initiated remotely. There is no available exploit. Applying a patch is the recommended action to fix this issue.
Details
A vulnerability, which was classified as critical, was found in Lichess lila 2025-06-02. This affects some unknown processing of the component Game Export API. The manipulation of the argument players with an unknown input leads to a server-side request forgery vulnerability. CWE is classifying the issue as CWE-918. The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Lichess lila before commit 11b4c0fb00f0ffd823246f839627005459c8f05c (2025-06-02) contains a Server-Side Request Forgery (SSRF) vulnerability in the game export API. The players parameter is passed directly to an internal HTTP client without validation, allowing remote attackers to force the server to send HTTP requests to arbitrary URLs
The advisory is shared at hackerone.com. This vulnerability is uniquely identified as CVE-2025-52186 since 06/16/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details are known, but no exploit is available.
Applying the patch 11b4c0fb00f0ffd8232346f839627005459c8f05 is able to eliminate this problem. The bugfix is ready for download at github.com.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
License
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Server-side request forgeryCWE: CWE-918
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: PatchStatus: 🔍
0-Day Time: 🔒
Patch: 11b4c0fb00f0ffd8232346f839627005459c8f05
Timeline
06/16/2025 CVE reserved11/13/2025 Advisory disclosed
11/13/2025 VulDB entry created
11/13/2025 VulDB entry last update
Sources
Advisory: hackerone.comStatus: Confirmed
CVE: CVE-2025-52186 (🔒)
GCVE (CVE): GCVE-0-2025-52186
GCVE (VulDB): GCVE-100-332373
Entry
Created: 11/13/2025 17:32Changes: 11/13/2025 17:32 (57)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.