{"answers":{"affected":"","exploited":"There is no known exploitation of CVE-2025-42616 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-42616 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-42616 is a high-severity vulnerability in CIRCL Vulnerability-Lookup, published on 8 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-42616 and fix it if it is affected.\n\nWhat it is: CVE-2025-42616 is a high-severity vulnerability in CIRCL Vulnerability-Lookup, published on 8 Dec 2025. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-42616 in the wild and no public exploit code.\n\nAffected product: CIRCL Vulnerability-Lookup. No package-level version data is available, so check the vendor advisory linked from the reference page.\n\nTask:\n1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.\n2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.\n3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.\n4. Run the tests and summarise what changed and why.\n5. If nothing in the project is affected, say so and change nothing.\n\nReference: https://insights.sbomify.com/CVE-2025-42616/ (Markdown: https://insights.sbomify.com/CVE-2025-42616/index.md)","id":"CVE-2025-42616","markdown":"https://insights.sbomify.com/CVE-2025-42616/index.md","name":"CVE-2025-42616","record":{"aliases":["GHSA-cr8j-9qv8-5jph"],"analysis":{"component_type":"web_application","fix_type":"upgrade","impacts":["privilege_escalation","data_modify"],"network_reachable":"yes","non_default_config":false,"product_category":"Vulnerability-Lookup","requires_auth":"high_privilege","summary":"Attackers can trick logged-in users into performing unauthorized state-changing actions via GET requests, leading to privilege escalation or data modification.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"ENISA","cpe":[],"cvss":{"score":7,"severity":"high","source":"cna","vector":"CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N","version":"4.0"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"Some endpoints in vulnerability-lookup that modified \napplication state (e.g. changing database entries, user data, \nconfigurations, or other privileged actions) may have been accessible \nvia HTTP GET requests without requiring a CSRF token. This flaw leaves \nthe application vulnerable to Cross-Site Request Forgery (CSRF) attacks:\n an attacker who tricks a logged-in user into visiting a malicious \nwebsite could cause the user’s browser to issue GET requests that \nperform unintended state-changing operations in the context of their \nauthenticated session.\n\nBecause the server would treat these GET requests as valid (since no \nCSRF protection or POST method enforcement was in place), the attacker \ncould exploit this to escalate privileges, change settings, or carry out\n other unauthorized actions without needing the user’s explicit consent \nor awareness. \nThe fix ensures that all state-changing endpoints now require HTTP POST \nrequests and include a valid CSRF token. This enforces that state \nchanges cannot be triggered by arbitrary cross-site GET requests. This issue affects Vulnerability-Lookup: before 2.18.0.","ecosystems":[],"exploits":{"exploitdb":0,"first_seen":null,"github_poc":0,"max_poc_stars":null,"metasploit":0,"nuclei":0,"refs":[],"tier":"none_known"},"has_fix":null,"headline":"CSRF vulnerability in CIRCL Vulnerability-Lookup","id":"CVE-2025-42616","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":1,"next":{"headline":"CSRF vulnerability in CIRCL Vulnerability-Lookup","id":"CVE-2025-42620"},"packages":[],"prev":{"headline":"Improper Restriction of Excessive Authentication Attempts vulnerability in CIRCL Vulnerability-Lookup","id":"CVE-2025-42615"},"products":["Vulnerability-Lookup"],"published":"2025-12-08","related":[],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"CWE Terms of Use","name":"CWE (MITRE)"},{"class":"attribution","licence":"FIRST CVSS licence","name":"CVSS (FIRST)"}],"ssvc":{"automatable":"no","exploitation":"none","technical_impact":"total"},"state":"PUBLISHED","updated":"2025-12-08","vendors":["CIRCL"]},"summary":"Attackers can trick logged-in users into performing unauthorized state-changing actions via GET requests, leading to privilege escalation or data modification.","url":"https://insights.sbomify.com/CVE-2025-42616/"}