{"answers":{"affected":"It affects 1 product.","exploited":"There is no known exploitation of CVE-2025-27912 in the wild and no public exploit code.","fix":"No fix has been published for CVE-2025-27912 yet. Limit exposure of the affected software until one is available.","what":"CVE-2025-27912 is a high-severity vulnerability in Datalust Seq, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link."},"fix_prompt":"Check this codebase for CVE-2025-27912 and fix it if it is affected.\n\nWhat it is: CVE-2025-27912 is a high-severity vulnerability in Datalust Seq, published on 11 Mar 2025. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.\nExploitation: There is no known exploitation of CVE-2025-27912 in the wild and no public exploit code.\n\nAffected product: Datalust Seq. 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-27912/ (Markdown: https://insights.sbomify.com/CVE-2025-27912/index.md)","id":"CVE-2025-27912","markdown":"https://insights.sbomify.com/CVE-2025-27912/index.md","name":"CVE-2025-27912","record":{"aliases":["GHSA-mpcp-p2wc-692j"],"analysis":{"component_type":"server_software","fix_type":"upgrade","impacts":["account_takeover","data_modify"],"network_reachable":"yes","non_default_config":true,"product_category":"Seq log server","requires_auth":"none","summary":"Attackers can perform actions on behalf of users via CSRF if specific authentication methods are enabled, requiring an upgrade to Seq.","user_interaction":"required","vuln_class":"csrf"},"analysis_generated_by":"qwen3.8-flash-next","assigner":"mitre","cpe":[{"product":"seq","vendor":"datalust"}],"cvss":{"score":8.8,"severity":"high","source":"cna","vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:H/RL:O/RC:C","version":"3.1"},"cwes":[{"id":"CWE-352","name":"Cross-Site Request Forgery"}],"description":"An issue was discovered in Datalust Seq before 2024.3.13545. Missing Content-Type validation can lead to CSRF when (1) Entra ID or OpenID Connect authentication is in use and a user visits a compromised/malicious site, or (2) when username/password or Active Directory authentication is in use and a user visits a compromised/malicious site under the same effective top-level domain as the Seq server. Exploitation of the vulnerability allows the attacker to conduct impersonation attacks and perform actions in Seq on behalf of the targeted user.","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":"Cross-site request forgery in Seq","id":"CVE-2025-27912","indexable":true,"kev":null,"kind":"cve","links":{"ecosystem":null,"product":null,"products":[],"type":"csrf","year":"2025"},"n_packages":0,"n_references":2,"next":{"headline":"Other in API","id":"CVE-2025-27913"},"packages":[],"prev":{"headline":"Denial of service in Seq","id":"CVE-2025-27911"},"products":["Seq"],"published":"2025-03-11","related":[{"cvss_score":9.8,"headline":"Auth bypass in n/a","id":"CVE-2018-8096","kev_date_added":null,"published":"2018-03-14"},{"cvss_score":9.1,"headline":"Privilege escalation in n/a","id":"CVE-2024-29866","kev_date_added":null,"published":"2024-03-21"},{"cvss_score":6.5,"headline":"Denial of service in Seq","id":"CVE-2025-27911","kev_date_added":null,"published":"2025-03-11"},{"cvss_score":6.5,"headline":"Information disclosure in n/a","id":"CVE-2021-41329","kev_date_added":null,"published":"2021-09-27"},{"cvss_score":5.7,"headline":"Denial of service in Seq","id":"CVE-2024-58102","kev_date_added":null,"published":"2025-03-11"},{"cvss_score":4.9,"headline":"Information disclosure in n/a","id":"CVE-2023-38195","kev_date_added":null,"published":"2023-07-22"}],"sources":[{"class":"attribution","licence":"CVE Terms of Use (MITRE)","name":"CVE List","prefix":"CVE"},{"class":"attribution","licence":"US public information, NVD API terms","name":"NVD"},{"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":"partial"},"state":"PUBLISHED","updated":"2025-03-11","vendors":["Datalust"]},"summary":"Attackers can perform actions on behalf of users via CSRF if specific authentication methods are enabled, requiring an upgrade to Seq.","url":"https://insights.sbomify.com/CVE-2025-27912/"}