dbcve.org
OS Command InjectionWeakness · CWE-78

CVE-2025-22469

HIGH · 7.3 CVSS v3.0 Published 2025-08-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
82/100
Remediation priority · High
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

OS command injection vulnerability in CL4/6NX Plus and CL4/6NX-J Plus (Japan model) network appliances allows execution of arbitrary OS commands with non-administrative user privileges due to insufficient input validation in firmware versions prior to 1.15.5-r1.

MitigationUpgrade firmware to version 1.15.5-r1 or later. If immediate patching is not possible, restrict network access to these devices and monitor for suspicious command execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify the device model
    Access the device administrative interface or check the device label to confirm the model is CL4/6NX Plus or CL4/6NX-J Plus (Japan model)
    Affected if The device is a CL4/6NX Plus or CL4/6NX-J Plus model
  2. Check the installed firmware version
    Log into the device administrative interface and navigate to the system status or firmware information page, or use the CLI command 'show version' or 'system status' if available
    Affected if The firmware version is lower than 1.15.5-r1 (for example, 1.14.x or earlier)
  3. Verify network accessibility of the management interface
    Confirm whether the device administrative or management interface is reachable from untrusted networks by checking network configuration, firewall rules, or by attempting to reach the management port from an external IP
    Affected if The management interface is exposed to the internet or untrusted internal networks
  4. Review logs for suspicious command execution
    Examine system logs, audit logs, or command history for entries involving the non-administrative user account, looking for unexpected or unauthorized command patterns
    Affected if Logs show commands executed by non-administrative users that were not initiated by legitimate administrative actions

A user is affected if they have a CL4/6NX Plus or CL4/6NX-J Plus device running firmware versions prior to 1.15.5-r1 with its management interface accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade firmware to version 1.15.5-r1 or later. If immediate patching is not possible, restrict network access to these devices and monitor for suspicious command execution.

Recommended fix Moderate confidence

firmware version 1.15.5-r1

  1. Identify the exact model number (CL4NX Plus, CL6NX Plus, or CL4NX-J Plus/CL6NX-J Plus) of the affected SATO printer
  2. Determine the current firmware version installed on the device (typically accessible through the printer's web interface or control panel)
  3. Download the firmware version 1.15.5-r1 or later from the official SATO support website (www.sato-global.com)
  4. Follow the manufacturer's firmware upgrade instructions specific to the model - this typically involves uploading the firmware file through the printer's web management interface or using SATO's configuration software
  5. After upgrading, verify the firmware version has been successfully updated to 1.15.5-r1 or later
  6. Confirm the vulnerability is remediated by verifying the specific non-administrative user account can no longer execute arbitrary OS commands
Caveat Review SATO release notes for any configuration or compatibility changes between your current version and 1.15.5-r1 before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,300
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-22469 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-22469 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data