CVE-2025-12278
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 · uneditedLogout Functionality not Working.This issue affects BLU-IC2: through 1.19.5; BLU-IC4: through 1.19.5.
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 · moderate confidenceThe logout functionality on BLU-IC2 and BLU-IC4 devices (versions through 1.19.5) does not properly terminate user sessions. When users attempt to log out, the session likely remains active server-side, allowing continued authenticated access without re-authentication. This is a session management vulnerability where session invalidation is not implemented or is faulty.
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< 1.20< 1.20CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N
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.
-
Check firmware version on BLU-IC2 deviceAccess the device management interface or use the firmware version check command (typically available via device status or system info page). Identify the installed firmware version.Affected if Firmware version is less than 1.20 (e.g., 1.19.5 or earlier).
-
Check firmware version on BLU-IC4 deviceAccess the device management interface or use the firmware version check command (typically available via device status or system info page). Identify the installed firmware version.Affected if Firmware version is less than 1.20 (e.g., 1.19.5 or earlier).
-
Verify session behavior after logoutLog into the device with valid credentials, perform a logout action, then attempt to use the previous session token or cookie to access protected resources or API endpoints without re-authenticating.Affected if Session token or session cookie remains valid and allows authenticated access after logout has been completed.
-
Inspect session management configurationCheck the device or backend configuration for session management settings, looking for session timeout, session invalidation, or session termination parameters related to logout functionality.Affected if Session invalidation is not implemented, is disabled, or is configured to retain active sessions after logout.
User is affected if the device firmware version is below 1.20 AND sessions remain valid after performing a logout action, allowing continued access without re-authentication.
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.
From vendor data1.20
Implement proper server-side session invalidation on logout that destroys the session token and clears any cached credentials, ensuring no continued access is possible after the logout action.
- Consultation3.0 h
- Implementation4.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 $3,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-12278 — 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-12278 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