/

CVE-2026-92984

Severity:

HIGH RISK

(8.1)

Session Fixation (CWE-384) in HUBzero CMS Web Platform

CVE-2026-92984

Deferred

Vulnerability type

Category:

Session Fixation

CWE:

CWE-384

Impact:

Account Takeover

Severity:

HIGH RISK

(8.1)

CVSS version:

3.1

Catch this CVE while code is being written

Detect vulnerable code directly in pull requests, so CVEs are fixed before merge.

Summary

HUBzero CMS accepts session identifiers from query strings and other request variables instead of relying exclusively on cookies. An unauthenticated attacker may cause a victim to authenticate with an attacker-known session identifier and then reuse that identifier to access the victim's account.

Affected context

The vulnerability may occur in HUBzero CMS deployments through version 2.2.32 when session management accepts identifiers from URL parameters or general request variables. Risk increases when an attacker can deliver a crafted link to a user and the application preserves the supplied identifier after authentication.

Exploit preconditions

  • Attack surface: Web-based authentication and session management
  • Required access: No prior authentication; the attacker must be able to obtain or establish a valid session identifier and deliver a link or request to a victim
  • Trigger point: Victim authentication while an attacker-controlled session identifier is accepted
  • Why exploitation is possible: The application may retain a session identifier supplied through a query string or request variable rather than issuing a fresh identifier after authentication

Why this happens

The underlying issue is inadequate session identifier lifecycle management. Accepting session identifiers from attacker-influenced request locations and failing to rotate them when authentication state changes maps to CWE-384: Session Fixation. This insecure pattern allows an attacker to learn or select a session identifier before authentication and benefit when a victim's authenticated state becomes associated with it.

Potential impact

  • An attacker could hijack a victim's authenticated session
  • Unauthorized access to account data and functionality may occur
  • Account settings or other user-controlled resources could be modified
  • Actions performed through the account could be attributed to the victim

General mitigation guidance

Mitigation generally focuses on making cookies the sole trusted session transport and enforcing a strict session lifecycle.

Common defensive patterns include:

  • Rejecting session identifiers supplied through query strings or untrusted request variables
  • Generating a new, unpredictable session identifier after authentication and privilege changes
  • Invalidating the pre-authentication session when authentication succeeds
  • Applying secure, HttpOnly, and appropriate SameSite cookie attributes
  • Limiting session lifetime and revoking sessions during logout or security-sensitive changes
  • Using least privilege for authenticated accounts and administrative functions

How teams detect issues like this

Organizations can identify session fixation risks through:

  • Static analysis and code review for session identifiers read from URL parameters or generic request variables
  • Tests verifying session identifier rotation after login, logout, and privilege changes
  • Dynamic testing that checks whether attacker-controlled identifiers remain valid after authentication
  • Web application firewall or gateway policies that reject session identifiers in unexpected request locations
  • Monitoring for repeated use of the same session identifier across pre-authentication and authenticated requests
  • Automated security review tools that flag unsafe session-management patterns

Sources

SourceLink
github.comgithub.com/hubzero/hubzero-cms
github.comgithub.com/hubzero/hubzero-cms/blob/v2.2.32/core/libraries/Hubzero/Session/Manager.php#L123-L132
github.comgithub.com/hubzero/hubzero-cms/commit/e60e8ebee5e1d38b1db1fc41bd9164b265b24356
vulncheck.comvulncheck.com/advisories/hubzero-cms-through-2.2.32-session-fixation-via-query-string-session-identifier

Frequently asked

questions

Yes. Exploitation can occur through normal web requests when an attacker can deliver a link or request containing a session identifier to a victim.

Not necessarily. The described condition is unauthenticated, although the attacker must obtain or establish a usable session identifier and cause the victim to authenticate within that session context.

Accept session identifiers through secure cookies only, reject attacker-controlled session sources, and rotate the identifier whenever authentication or privilege state changes.

Include session lifecycle tests in security reviews, enforce secure cookie policies, invalidate pre-authentication sessions after login, and monitor for suspicious token reuse.

Find out what's already
exploitable in your codebase.