# CVE-2023-23594: Auth bypass in n/a

> Remote attackers can bypass authentication on CL4NX printers to execute privileged commands like file uploads and configuration changes.

- **Severity:** Critical 9.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 31 Mar 2023
- **Updated:** 18 Feb 2025
- **Also known as:** GHSA-q969-vw55-r9vr

## What is CVE-2023-23594?

CVE-2023-23594 is a critical authentication bypass vulnerability in n/a, published on 31 Mar 2023. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

An authentication bypass vulnerability in the web client interface for the CL4NX printer before firmware version 1.13.3-u724_r2 provides remote unauthenticated attackers with access to execute commands intended only for valid/authenticated users, such as file uploads and configuration changes.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2023-23594?

It affects 1 product.


Products: Sato-Global Cl4nx Plus Firmware.

## How do I fix CVE-2023-23594?

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

## Is CVE-2023-23594 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2023-23594 and fix it if it is affected.

What it is: CVE-2023-23594 is a critical authentication bypass vulnerability in n/a, published on 31 Mar 2023. 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-2023-23594 in the wild and no public exploit code.

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

## Sources

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

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