CVE-2025-27912
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedAn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceDatalust Seq before version 2024.3.13545 lacks proper Content-Type validation on requests, enabling Cross-Site Request Forgery (CSRF) attacks. When users authenticated via Entra ID, OpenID Connect, username/password, or Active Directory visit a malicious site under the same effective top-level domain, attackers can craft malicious requests that execute actions in Seq on behalf of the authenticated user, leading to impersonation and unauthorized operations.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 2024.3.13545CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Locate the Seq installationIdentify where Seq is installed; common paths include /opt/seq on Linux, C:\Program Files\Seq on Windows, or check running containers for the seq imageAffected if Seq is installed on the system
-
Determine the installed Seq versionRun 'seq' from the command line with no arguments or check the Seq log file (seq.txt in the installation directory) for the version string at startup, or query the /api/rootsummary endpoint on a running Seq instanceAffected if The version shown is less than 2024.3.13545 (e.g., 2024.3.12345, 2024.2.x, or earlier)
-
Verify authentication method in useCheck Seq settings or configuration for the configured authentication provider (Entra ID, OpenID Connect, username/password, or Active Directory)Affected if Any of these authentication methods are configured, as all are affected by the CSRF flaw
-
Confirm the deployment is accessible over HTTP/HTTPSVerify the Seq URL is reachable and check the HTTP response headers or web interfaceAffected if Seq is accessible over the network (the CSRF attack requires the user to make requests to the Seq server)
You are affected if Seq is installed and the running version is earlier than 2024.3.13545, regardless of which supported authentication method is configured.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2024.3.13545
Upgrade Datalust Seq to version 2024.3.13545 or later to address the missing Content-Type validation. This is the definitive fix; there are no practical workarounds for CSRF vulnerabilities of this nature.
2024.3.13545
- Upgrade Seq to version 2024.3.13545 or later
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,512.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27912 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-27912 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data