# CVE-2025-22469: Command injection in CL4/6NX Plus

> Attackers with low privileges can execute arbitrary OS commands on SATO label printers via an OS command injection vulnerability.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Aug 2025
- **Updated:** 6 Aug 2025
- **Also known as:** GHSA-r6vq-w38v-3h79

## What is CVE-2025-22469?

CVE-2025-22469 is a medium-severity command injection vulnerability in SATO Corporation CL4/6NX Plus, published on 6 Aug 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

OS command injection vulnerability exists in CL4/6NX Plus and CL4/6NX-J Plus (Japan model) with the firmware versions prior to 1.15.5-r1. An arbitrary OS command may be executed on the system with a certain non-administrative user privilege.

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

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


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

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

## Is CVE-2025-22469 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-22469 is a medium-severity command injection vulnerability in SATO Corporation CL4/6NX Plus, published on 6 Aug 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-22469 in the wild and no public exploit code.

Affected product: SATO Corporation CL4/6NX Plus. 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-22469/ (Markdown: https://insights.sbomify.com/CVE-2025-22469/index.md)
```

## Sources

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

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