# CVE-2026-92920: admin3 through 3.0.0 Session Not Invalidated When a User Account Is Disabled

> Attackers retain authenticated access with original permissions after account disablement because existing sessions are not invalidated.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-xx9v-9858-mwgg

## What is CVE-2026-92920?

CVE-2026-92920 is a medium-severity authentication bypass vulnerability in cjbi admin3, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

admin3 through 3.0.0 fails to invalidate existing sessions when disabling a user account, allowing attackers to retain authenticated access with original permissions. Attackers can continue using bearer tokens issued before account disablement to authenticate requests, as the AuthInterceptor never re-validates the user's locked status and session expiry resets on each request.

Weakness: CWE-613 (DEPRECATED: Insufficient Session Expiration)

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


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

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

## Is CVE-2026-92920 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92920 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92920 is a medium-severity authentication bypass vulnerability in cjbi admin3, published on 17 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92920 exists.

Affected product: cjbi admin3. 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-92920/ (Markdown: https://insights.sbomify.com/CVE-2026-92920/index.md)
```

## Sources

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

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