{“lastseen”:””,”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\u2019s browser to issue GET requests that \\nperform unintended state-changing operations in the context of their \\nauthenticated session.\\n\\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\u2019s explicit consent \\nor awareness.\u00a0\\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.\u00a0This issue affects Vulnerability-Lookup: before 2.18.0.”,”published”:”2025-12-08T12:09:22.893Z”,”modified”:”2025-12-08T12:58:58.408Z”,”type”:”cve”,”title”:”CSRF vulnerability in CIRCL Vulnerability-Lookup”,”source”:”ENISA”,”references”:”https:\/\/vulnerability.circl.lu\/vuln\/gcve-1-2025-0034″,”id”:”CVE-2025-42616″,”bulletinFamily”:””,”cwe”:[“CWE-352″],”cvelist”:null,”sourceData”:”CIRCL Vulnerability-Lookup 0″,”sourceHref”:””,”cvss”:{“score”:7,”severity”:”HIGH”,”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″},”cvss2″:{},”cvss3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””,”cvssV3″:{“version”:””,”vectorString”:””,”baseScore”:0,”baseSeverity”:””,”attackVector”:””,”attackComplexity”:””,”privilegesRequired”:””,”userInteraction”:””,”scope”:””,”confidentialityImpact”:””,”integrityImpact”:””,”availabilityImpact”:””}},”href”:””,”category_name”:”CVE”,”post_link”:””,”product”:”Vulnerability-Lookup”,”version”:”0″,”vendor”:”CIRCL”,”ai_description”:””,”ai_severity”:””,”ai_vendor”:””,”ai_product”:””,”ai_version”:””,”ai_score”:0}<\/p>\n","protected":false},"excerpt":{"rendered":"
{“lastseen”:””,”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…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[2],"tags":[6,8,79,12,15,13,7,11,5],"class_list":["post-29295","post","type-post","status-publish","format-standard","hentry","category-category_cve","tag-cve","tag-cvss","tag-cvss-70","tag-exploit","tag-high","tag-news","tag-security","tag-tapic","tag-vulnerability"],"yoast_head":"\n