dbcve.org
BluditApplication

CVE-2026-25101

CRITICAL · 9.8 CVSS v3.1 Published 2026-03-27
Fix available
A fix is available. Upgrade to 3.17.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
Bludit allows user's session identifier to be set before authentication. The value of this session ID stays the same after authentication. This behavior enables an attacker to fix a session ID for a victim and later hijack the authenticated session. This issue was fixed in version 3.17.2.

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 confidence

Bludit CMS suffers from a session fixation vulnerability where an attacker can pre-set a user's session identifier before authentication occurs. The session ID remains unchanged after successful authentication, allowing the attacker to hijack the authenticated session by leveraging the known session ID.

MitigationUpgrade Bludit to version 3.17.2 or later to remediate this session fixation vulnerability.

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
BluditApplication
Affected:< 3.17.2

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Bludit version
    Locate the version file or check the admin dashboard for the current Bludit version number. Common locations include a version.php file in the root directory or the About section in the admin panel.
    Affected if The installed version is lower than 3.17.2 (for example, 3.17.1, 3.16.0, or earlier versions).
  2. Inspect session initialization behavior
    Examine the session handling code that runs before user authentication. Look for any endpoint or parameter that allows setting a custom session identifier prior to the login process.
    Affected if The application accepts or uses a user-provided session ID before authentication without generating a new one.
  3. Verify session regeneration after login
    Check whether the session ID is regenerated (a new session is created) immediately after a successful authentication event. Compare the session ID before and after logging in.
    Affected if The session ID remains unchanged after successful authentication - the same session ID used before login continues to be used after the user authenticates.
  4. Review session configuration settings
    Examine the session configuration files or settings within Bludit to determine if session fixation protections are enabled, such as regenerating session IDs on login.
    Affected if Session regeneration on login is disabled or not implemented in the configuration.

You are affected if your installed Bludit version is below 3.17.2 AND the session ID is not regenerated upon successful authentication, allowing an attacker to fix a session ID before a user logs in and then hijack that authenticated session.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 3.17.2 or later
Fixed in 3.17.2
Interim mitigation

Upgrade Bludit to version 3.17.2 or later to remediate this session fixation vulnerability.

Recommended fix High confidence

3.17.2

  1. Create a complete backup of the Bludit installation directory and database
  2. Download Bludit version 3.17.2 from the official Bludit repository or website
  3. Replace all existing Bludit files with the files from version 3.17.2, preserving any custom configuration files if needed
  4. Verify the upgrade was successful by checking the installed version in the admin dashboard or via the version file
  5. Test the authentication flow to confirm session handling works correctly and the session ID changes after login

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Bludit Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25101 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-25101 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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