# CVE-2022-41807: Missing authorization in Kyocera Document Solutions MFPs and printers

> A network-adjacent attacker can alter device settings without authentication due to missing authorization checks in Kyocera MFPs and printers.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:A/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 5 Dec 2022
- **Updated:** 24 Apr 2025
- **Also known as:** GHSA-26rq-fvc6-cmqf

## What is CVE-2022-41807?

CVE-2022-41807 is a medium-severity missing authorization vulnerability in Kyocera Document Solutions MFPs and printers, published on 5 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

Missing authorization vulnerability exists in Kyocera Document Solutions MFPs and printers, which may allow a network-adjacent attacker to alter the product settings without authentication by sending a specially crafted request. Affected products/versions are as follows: TASKalfa 7550ci/6550ci, TASKalfa 5550ci/4550ci/3550ci/3050ci, TASKalfa 255c/205c, TASKalfa 256ci/206ci, ECOSYS M6526cdn/M6526cidn, FS-C2126MFP/C2126MFP+/C2026MFP/C2026MFP+, TASKalfa 8000i/6500i, TASKalfa 5500i/4500i/3500i, TASKalfa 305/255, TASKalfa 306i/256i, LS-3140MFP/3140MFP+/3640MFP, ECOSYS M2535dn, LS-1135MFP/1035MFP, LS-C8650DN/C8600DN, ECOSYS P6026cdn, FS-C5250DN, LS-4300DN/4200DN/2100DN, ECOSYS P4040dn, ECOSYS P2135dn, and FS-1370DN.

Weakness: CWE-862 (Missing Authorization)

## Which versions are affected by CVE-2022-41807?

It affects 40 products.


Products: Kyocera Ecosys M2535dn Firmware, Kyocera Ecosys M6526cdn Firmware, Kyocera Ecosys M6526cidn Firmware, Kyocera Ecosys P2135dn Firmware, Kyocera Ecosys P4040dn Firmware, Kyocera Ecosys P6026cdn Firmware, Kyocera Fs-1370dn Firmware, Kyocera Fs-C2026mfp Firmware, Kyocera Fs-C2126mfp\+ Firmware, Kyocera Fs-C2126mfp Firmware, Kyocera Fs-C5250dn Firmware, Kyocera Ls-1035mfp Firmware, Kyocera Ls-1135mfp Firmware, Kyocera Ls-2100dn Firmware, Kyocera Ls-3140mfp\+ Firmware, Kyocera Ls-3140mfp Firmware, Kyocera Ls-3640mfp Firmware, Kyocera Ls-4200dn Firmware, Kyocera Ls-4300dn Firmware, Kyocera Ls-C8600dn Firmware and 20 more.

## How do I fix CVE-2022-41807?

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

## Is CVE-2022-41807 being exploited?

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

## Other vulnerabilities in Kyocera Document Solutions MFPs and printers

- [CVE-2022-41798](https://insights.sbomify.com/CVE-2022-41798/): Auth bypass in Kyocera Document Solutions MFPs and printers (medium 6.5)
- [CVE-2022-41830](https://insights.sbomify.com/CVE-2022-41830/): Cross-site scripting in Kyocera Document Solutions MFPs and printers (medium 4.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-41807 and fix it if it is affected.

What it is: CVE-2022-41807 is a medium-severity missing authorization vulnerability in Kyocera Document Solutions MFPs and printers, published on 5 Dec 2022. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-41807 in the wild and no public exploit code.

Affected product: Kyocera Document Solutions MFPs and printers. 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-2022-41807/ (Markdown: https://insights.sbomify.com/CVE-2022-41807/index.md)
```

## Sources

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

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