# CVE-2026-92921: admin3 through 3.0.0 Weak Password Hashing via Single-Round MD5

> Attackers with database access can recover plaintext passwords via offline attacks due to weak single-round MD5 hashing in admin3.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-99pq-pxmq-gf2q

## What is CVE-2026-92921?

CVE-2026-92921 is a medium-severity vulnerability in cjbi admin3, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

admin3 through 3.0.0 stores account passwords using single-round MD5 with only the username as salt and no key derivation function. Attackers with database access can recover plaintext passwords through offline dictionary or brute-force attacks due to negligible computational effort.

Weakness: CWE-916 (Use of Password Hash With Insufficient Computational Effort)

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


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

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

## Is CVE-2026-92921 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-92921 is a medium-severity vulnerability in cjbi admin3, published on 17 Sep 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-92921 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-92921/ (Markdown: https://insights.sbomify.com/CVE-2026-92921/index.md)
```

## Sources

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

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