# CVE-2025-60595: Command injection in n/a

> Arbitrary code execution vulnerability in SPH Engineering UgCS allows attackers to run malicious commands on the host system.

- **Severity:** High 8.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 29 Oct 2025
- **Updated:** 30 Oct 2025
- **Also known as:** GHSA-55f4-6pv4-vw79

## What is CVE-2025-60595?

CVE-2025-60595 is a high-severity command injection vulnerability in n/a, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SPH Engineering UgCS 5.13.0 is vulnerable to Arbitary code execution.

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

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


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

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

## Is CVE-2025-60595 being exploited?

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

Public exploit code:

- SPH Engineering UgCS 5.13.0 is vulnerable to Arbitary code execution. This is the public refrence to be used on CVE site (github_poc): https://github.com/bilalclicksafe/CVE-2025-60595

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60595 is a high-severity command injection vulnerability in n/a, published on 29 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-60595 in the wild and no public exploit code.

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

## Sources

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

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