# CVE-2026-124578: Pantum BP5100DW Web omDB.shtml missing authentication


- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:X`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 9 Nov 2026
- **Updated:** 10 Nov 2026
- **Also known as:** GHSA-5g96-mq2h-p82p

## What is CVE-2026-124578?

CVE-2026-124578 is a medium-severity vulnerability in Pantum BP5100DW, published on 9 Nov 2026. 

### Official description

A security vulnerability has been detected in Pantum BP5100DW 3.A.4.7. The impacted element is an unknown function of the file /shtml/omDB.shtml of the component Web Interface. The manipulation leads to missing authentication. The attack may be initiated remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-306 (Missing Authentication for Critical Functionality), CWE-287 (Improper Authentication)

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


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

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

## Is CVE-2026-124578 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-124578 is a medium-severity vulnerability in Pantum BP5100DW, published on 9 Nov 2026. 
Exploitation: There is no known exploitation of CVE-2026-124578 in the wild and no public exploit code.

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

## Sources

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

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