# CVE-2026-91853: TOTOLINK X5000R Export Ovpn cstecgi.cgi exportOvpn os command injection

> Remote attackers can execute arbitrary OS commands via the exportOvpn handler in TOTOLINK X5000R routers, requiring authentication.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:L/SI:L/SA:L/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Sep 2026
- **Updated:** 15 Sep 2026
- **Also known as:** GHSA-q4rv-4ppf-7295

## What is CVE-2026-91853?

CVE-2026-91853 is a medium-severity command injection vulnerability in TOTOLINK X5000R, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability has been found in TOTOLINK X5000R 9.1.0cu.2089_B20211224. The impacted element is the function exportOvpn of the file /cgi-bin/cstecgi.cgi?action=exportOvpn&type=user of the component Export Ovpn Handler. The manipulation of the argument filetype leads to os command injection. The attack can be initiated remotely. The exploit has been disclosed to the public and may be used.

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

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


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

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

## Is CVE-2026-91853 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-91853 is a medium-severity command injection vulnerability in TOTOLINK X5000R, published on 15 Sep 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-91853 exists.

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

## Sources

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

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