# CVE-2025-59817: Authenticated Remote Code Execution in zForm_auto_config

> Authenticated attackers can execute arbitrary commands with root privileges on Zenitel TCIS-3+ devices, leading to full system compromise.

- **Severity:** High 8.4 (`CVSS:3.1/AV:A/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Sep 2025
- **Updated:** 29 Sep 2025
- **Also known as:** GHSA-22pg-w2f6-xfjw

## What is CVE-2025-59817?

CVE-2025-59817 is a high-severity command injection vulnerability in Zenitel TCIS-3+, published on 25 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

This vulnerability allows attackers to execute arbitrary commands on the underlying system. Because the web portal runs with root privileges, successful exploitation grants full control over the device, potentially compromising its availability, confidentiality, and integrity.

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

## Which versions are affected by CVE-2025-59817?


## How do I fix CVE-2025-59817?

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

## Is CVE-2025-59817 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-59817 and fix it if it is affected.

What it is: CVE-2025-59817 is a high-severity command injection vulnerability in Zenitel TCIS-3+, published on 25 Sep 2025. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-59817 in the wild and no public exploit code.

Affected product: Zenitel TCIS-3+. 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-2025-59817/ (Markdown: https://insights.sbomify.com/CVE-2025-59817/index.md)
```

## Sources

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

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