# CVE-2026-56808: Command injection in DGM3103SCT

> Authenticated users can execute arbitrary commands with root privileges via OS command injection in the web management console.

- **Severity:** High 8.6 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/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:** 30 Jun 2026
- **Updated:** 30 Jun 2026
- **Also known as:** GHSA-xqc8-pr7j-cj3w

## What is CVE-2026-56808?

CVE-2026-56808 is a high-severity command injection vulnerability in AVTECH Security Corporation DGM3103SCT, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

DGM3103SCT provided by AVTECH Security Corporation contains an OS command injection vulnerability, which may lead to arbitrary command execution with the root privilege by a user who can log in to the web management console of the affected product.

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

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


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

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

## Is CVE-2026-56808 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-56808 is a high-severity command injection vulnerability in AVTECH Security Corporation DGM3103SCT, published on 30 Jun 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-56808 in the wild and no public exploit code.

Affected product: AVTECH Security Corporation DGM3103SCT. 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-56808/ (Markdown: https://insights.sbomify.com/CVE-2026-56808/index.md)
```

## Sources

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

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