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-2025-52186: n/a

0
Medium
VulnerabilityCVE-2025-52186cvecve-2025-52186
Published: Thu Nov 13 2025 (11/13/2025, 00:00:00 UTC)
Source: CVE Database V5

Description

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

AI-Powered Analysis

AILast updated: 11/13/2025, 15:50:47 UTC

Technical Analysis

CVE-2025-52186 is a Server-Side Request Forgery (SSRF) vulnerability identified in the Lichess lila platform before commit 11b4c0fb00f0ffd823246f839627005459c8f05c, published on November 13, 2025. The vulnerability exists in the game export API, specifically in the handling of the 'players' parameter. This parameter is passed directly to an internal HTTP client without any validation or sanitization, enabling remote attackers to craft requests that cause the server to initiate HTTP requests to arbitrary URLs. SSRF vulnerabilities allow attackers to bypass firewall restrictions and access internal resources that are not directly accessible from the internet. Potential exploitation scenarios include scanning internal networks, accessing metadata services in cloud environments, or interacting with internal APIs, which can lead to information disclosure or further compromise. The vulnerability does not require authentication or user interaction, increasing its risk profile. Although no public exploits have been reported, the lack of input validation and the direct use of user-supplied data in HTTP requests make this vulnerability straightforward to exploit. The affected software is Lichess lila, an open-source chess platform widely used for online chess play and analysis. The absence of a CVSS score necessitates a severity assessment based on impact and exploitability factors.

Potential Impact

For European organizations, the impact of CVE-2025-52186 can be significant, especially for those hosting their own Lichess lila instances or integrating the platform into their services. Exploitation could allow attackers to perform internal network reconnaissance, potentially exposing sensitive internal services or data repositories. This could lead to unauthorized access to confidential information, disruption of internal services, or serve as a pivot point for further attacks within the organization's network. Organizations using cloud infrastructure may be particularly vulnerable if the SSRF can be leveraged to access cloud metadata services, leading to credential theft or privilege escalation. The vulnerability's ability to be exploited without authentication increases the risk of automated attacks and broad scanning. Given the popularity of Lichess in Europe and the potential for internal network exposure, this vulnerability could affect educational institutions, chess federations, and private companies using the platform. The absence of known exploits currently limits immediate widespread impact, but the risk remains high due to the nature of SSRF vulnerabilities.

Mitigation Recommendations

To mitigate CVE-2025-52186, organizations should immediately update Lichess lila to the fixed version that includes the commit 11b4c0fb00f0ffd823246f839627005459c8f05c or later. If updating is not immediately possible, implement strict input validation and sanitization on the 'players' parameter to ensure only expected and safe URLs or identifiers are accepted. Employ network-level controls to restrict outbound HTTP requests from the Lichess server to only trusted destinations, minimizing the risk of SSRF exploitation. Use web application firewalls (WAFs) with rules designed to detect and block SSRF attack patterns. Monitor server logs for unusual outbound HTTP requests or patterns indicative of SSRF attempts. Additionally, conduct internal network segmentation to limit the exposure of sensitive services to the Lichess server. Regularly audit and review the platform's API endpoints for similar vulnerabilities and apply secure coding practices to prevent injection of untrusted data into internal requests.

Need more detailed analysis?Get Pro

Technical Details

Data Version
5.2
Assigner Short Name
mitre
Date Reserved
2025-06-16T00:00:00.000Z
Cvss Version
null
State
PUBLISHED

Threat ID: 6915fac277eaf5a8495aabda

Added to database: 11/13/2025, 3:35:30 PM

Last enriched: 11/13/2025, 3:50:47 PM

Last updated: 11/14/2025, 4:11:08 AM

Views: 5

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 enhanced features?

Contact root@offseq.com for Pro access with improved analysis and higher rate limits.

Latest Threats