# CVE-2026-78211: 4MOSAn Security Technology｜4MOSAn GCB Doctor - OS Command Injection

> Unauthenticated attackers can execute arbitrary system commands via an exposed ADOdb test page parameter in 4MOSAn GCB Doctor.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Aug 2026
- **Updated:** 24 Aug 2026
- **Also known as:** GHSA-5jrp-qhfh-7jjg

## What is CVE-2026-78211?

CVE-2026-78211 is a critical command injection vulnerability in 4MOSAn GCB Doctor, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

4MOSAn GCB Doctor developed by 4MOSAn Security Technology has a OS Command Injection vulnerability. Unauthenticated remote attackers can inject malicious commands through an unremoved ADOdb test page parameter, thereby executing arbitrary system commands on the server.

Weakness: CWE-78 (Improper Neutralization of Special Elements used in an OS Command)

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


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

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

## Is CVE-2026-78211 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-78211 is a critical command injection vulnerability in 4MOSAn GCB Doctor, published on 24 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-78211 in the wild and no public exploit code.

Affected product: 4MOSAn GCB Doctor. 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-78211/ (Markdown: https://insights.sbomify.com/CVE-2026-78211/index.md)
```

## Sources

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

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