CVE-2025-42616: CSRF vulnerability in CIRCL Vulnerability-Lookup
Some endpoints in vulnerability-lookup that modified application state (e.g. changing database entries, user data, configurations, or other privileged actions) may have been accessible via HTTP GET requests without requiring a CSRF token. This flaw leaves the application vulnerable to Cross-Site Request Forgery (CSRF) attacks: an attacker who tricks a logged-in user into visiting a malicious website could cause the user’s browser to issue GET requests that perform unintended state-changing operations in the context of their authenticated session.
Because the server would treat these GET requests as valid (since no CSRF protection or POST method enforcement was in place), the attacker could exploit this to escalate privileges, change settings, or carry out other unauthorized actions without needing the user’s explicit consent or awareness. The fix ensures that all state-changing endpoints now require HTTP POST requests and include a valid CSRF token. This enforces that state changes cannot be triggered by arbitrary cross-site GET requests. This issue affects Vulnerability-Lookup: before 2.18.0.
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade
CIRCL Vulnerability-Lookupto a version that resolves this vulnerability.Fixed in 2.18.0
Event History
Frequently Asked Questions
What is the severity of CVE-2025-42616?
CVE-2025-42616 is classified as a high severity vulnerability due to potential unauthorized modifications of application state.
How do I fix CVE-2025-42616?
To fix CVE-2025-42616, implement CSRF protection on affected endpoints to ensure state-modifying actions require a valid CSRF token.
What software is affected by CVE-2025-42616?
CVE-2025-42616 affects the git/circl application where certain endpoints may be accessed insecurely.
What kind of attacks can CVE-2025-42616 enable?
CVE-2025-42616 can enable Cross-Site Request Forgery (CSRF) attacks, allowing attackers to perform unauthorized actions on behalf of users.
What types of data can be compromised due to CVE-2025-42616?
CVE-2025-42616 can lead to unauthorized changes in database entries, user data, and configuration settings.