# CVE-2026-113389: DrayTek Vigor2960 CGI Process mainfunction.cgi set_table command injection


- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H/E:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 20 Oct 2026
- **Updated:** 20 Oct 2026
- **Also known as:** GHSA-93hq-w565-c2gv

## What is CVE-2026-113389?

CVE-2026-113389 is a critical vulnerability in DrayTek Vigor2960, published on 20 Oct 2026. 

### Official description

A vulnerability was detected in DrayTek Vigor2960 1.5.1.6 Revision 8218. Affected by this vulnerability is the function set_table of the file /cgi-bin/mainfunction.cgi of the component CGI Process. The manipulation of the argument sectiontype results in command injection. The attack may be launched remotely. The exploit is now public and may be used. The vendor explains: "2960 1.5.1.7 has corrected many security issues. And 2960 is EoS with limited support, only major issues would be reviewed(e.g. unauthenticated vuln.)". This vulnerability only affects products that are no longer supported by the maintainer.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command), CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component)

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


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

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

## Is CVE-2026-113389 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-113389 is a critical vulnerability in DrayTek Vigor2960, published on 20 Oct 2026. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-113389 exists.

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

## Sources

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

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