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

> Local attackers can inject arbitrary OS commands via the IP Addr parameter in the Curo UC300 Admin panel.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/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:** 8 Oct 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-63j3-6953-p6pv

## What is CVE-2025-57457?

CVE-2025-57457 is a high-severity command injection vulnerability in n/a, published on 8 Oct 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An OS Command Injection vulnerability in the Admin panel in Curo UC300 5.42.1.7.1.63R1 allows local attackers to inject arbitrary OS Commands via the "IP Addr" parameter.

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

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


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

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

## Is CVE-2025-57457 being exploited?

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

Public exploit code:

- https://github.com/restdone/CVE-2025-57457 (github_poc): https://github.com/restdone/CVE-2025-57457

## Fix prompt for AI coding agents

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

What it is: CVE-2025-57457 is a high-severity command injection vulnerability in n/a, published on 8 Oct 2025. 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-2025-57457 exists.

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

## Sources

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

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