CVE-2025-22470
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 · uneditedCL4/6NX Plus and CL4/6NX-J Plus (Japan model) with the firmware versions prior to 1.15.5-r1 allow crafted dangerous files to be uploaded. An arbitrary Lua script may be executed on the system with the root 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 confidenceA pre-authentication file upload vulnerability in CL4/6NX Plus and CL4/6NX-J Plus network appliances allows attackers to upload crafted malicious files containing arbitrary Lua scripts. These scripts execute with root privileges, enabling complete system compromise.
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
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
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 checksWork through these to decide whether this CVE applies to you.
-
Identify the network appliance modelAccess the device web interface or CLI and retrieve the exact model name (CL4NX Plus, CL6NX Plus, CL4NX-J Plus, or CL6NX-J Plus). In CLI, this is typically shown in startup banners or via 'show version' or 'show model' commands.Affected if The model is CL4NX Plus, CL6NX Plus, CL4NX-J Plus, or CL6NX-J Plus (any of the four affected models).
-
Retrieve the current firmware versionCheck the device firmware version through the web interface (typically under System > Status or Administration > Firmware) or via CLI command such as 'show version' or 'fwver'. Compare the version number to 1.15.5-r1.Affected if The installed firmware version is earlier than 1.15.5-r1 (versions 1.x.y below this release are affected).
-
Confirm the file upload web interface is accessibleAttempt to access the file upload endpoint (typically /cgi-bin/upload or similar) without authentication. Check if the endpoint responds without requiring login credentials.Affected if The file upload interface responds to unauthenticated requests, indicating the pre-authentication attack surface is exposed.
-
Inspect for suspicious uploaded filesCheck the device file system for unexpected .lua files in web-accessible directories (commonly /www, /var/www, /cgi-bin, or /tmp). Use CLI 'ls' or 'find' commands to locate any recently created Lua scripts.Affected if Unexpected .lua script files exist on the device, particularly in directories accessible via the web interface.
If the device is a CL4/6NX Plus or CL4/6NX-J Plus model running firmware earlier than 1.15.5-r1 and the unauthenticated file upload endpoint is accessible, the environment is affected by this vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scopedUpgrade firmware to version 1.15.5-r1 or later to remediate the file upload vulnerability. Apply during a scheduled maintenance window and verify the update was applied successfully.
1.15.5-r1
- Identify the current firmware version of the CL4/6NX Plus or CL4/6NX-J Plus device
- Obtain firmware version 1.15.5-r1 or later from the official SATO vendor support website
- Follow the vendor's documented firmware update procedure to apply the update to the affected device
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-22470 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-22470 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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