# CVE-2025-67738: Command injection in Webmin

> An authenticated attacker with Cache Manager permissions can execute arbitrary commands via improper argument quoting in the Squid Cache Manager interface.

- **Severity:** High 8.5 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:C/C:H/I:H/A:H`)
- **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:** 11 Dec 2025
- **Updated:** 18 Dec 2025
- **Also known as:** GHSA-gq3p-5rgr-j77q

## What is CVE-2025-67738?

CVE-2025-67738 is a high-severity command injection vulnerability in Webmin, published on 11 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

squid/cachemgr.cgi in Webmin before 2.600 does not properly quote arguments. This is relevant if Webmin's Squid module and its Cache Manager feature are available, and an untrusted party is able to authenticate to Webmin and has certain Cache Manager permissions (the "cms" security option).

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

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


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

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

## Is CVE-2025-67738 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-67738 is a high-severity command injection vulnerability in Webmin, published on 11 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-67738 in the wild and no public exploit code.

Affected product: Webmin. 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-67738/ (Markdown: https://insights.sbomify.com/CVE-2025-67738/index.md)
```

## Sources

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

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