# CVE-2025-54958: Command injection in Powered BLUE 870

> An OS command injection vulnerability in Powered BLUE 870 allows attackers to execute arbitrary OS commands on the affected device.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **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 Aug 2025
- **Updated:** 8 Aug 2025
- **Also known as:** GHSA-22m7-f932-qh5j

## What is CVE-2025-54958?

CVE-2025-54958 is a medium-severity command injection vulnerability in Mubit co.,ltd. Powered BLUE 870, published on 8 Aug 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Powered BLUE 870 versions 0.20130927 and prior contain an OS command injection vulnerability. If this vulnerability is exploited, arbitrary OS commands may be executed on the affected product.

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

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


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

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

## Is CVE-2025-54958 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-54958 is a medium-severity command injection vulnerability in Mubit co.,ltd. Powered BLUE 870, published on 8 Aug 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-54958 in the wild and no public exploit code.

Affected product: Mubit co.,ltd. Powered BLUE 870. 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-54958/ (Markdown: https://insights.sbomify.com/CVE-2025-54958/index.md)
```

## Sources

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

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