# CVE-2025-47228: Command injection in ScriptCase

> Authenticated attackers can execute arbitrary system commands via crafted HTTP requests in the SSH connection settings of ScriptCase.

- **Severity:** Medium 6.7 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Jul 2025
- **Updated:** 7 Jul 2025
- **Also known as:** GHSA-pfxq-29cx-gm9c

## What is CVE-2025-47228?

CVE-2025-47228 is a medium-severity command injection vulnerability in ScriptCase, published on 5 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

In the Production Environment extension in Netmake ScriptCase through 9.12.006 (23), shell injection in the SSH connection settings allows authenticated attackers to execute system commands via crafted HTTP requests.

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

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


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

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

## Is CVE-2025-47228 being exploited?

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

Public exploit code:

- ScriptCase 9.12.006 (23) - Remote Command Execution (RCE) (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47228 is a medium-severity command injection vulnerability in ScriptCase, published on 5 Jul 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-47228 exists.

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

## Sources

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

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