# CVE-2026-92984: HUBzero CMS through 2.2.32 Session Fixation via Query-String Session Identifier

> Attackers can hijack user accounts by fixing session identifiers via query strings in HUBzero CMS, allowing unauthorized access after victim authentication.

- **Severity:** High 8.5 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 21 Sep 2026
- **Also known as:** GHSA-jq63-mx4g-ww7g

## What is CVE-2026-92984?

CVE-2026-92984 is a high-severity authentication bypass vulnerability in hubzero-cms, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

HUBzero CMS through 2.2.32 accepts session identifiers from query strings and request variables instead of cookies alone, allowing unauthenticated attackers to fixate victim sessions. Attackers can obtain a valid session identifier, send victims a crafted link containing it, and replay the identifier after the victim authenticates to hijack their account and access.

Weakness: CWE-384 (Session Fixation)

## Which versions are affected by CVE-2026-92984?


## How do I fix CVE-2026-92984?

No fix has been published for CVE-2026-92984 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-92984 being exploited?

There is no known exploitation of CVE-2026-92984 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-92984 and fix it if it is affected.

What it is: CVE-2026-92984 is a high-severity authentication bypass vulnerability in hubzero-cms, published on 17 Sep 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2026-92984 in the wild and no public exploit code.

Affected product: hubzero-cms. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. 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.
2. 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.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-92984/ (Markdown: https://insights.sbomify.com/CVE-2026-92984/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-92984
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-92984
- OSV: https://osv.dev/vulnerability/CVE-2026-92984

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-92984/
Summaries are generated and may contain mistakes; the official description above is the record.