# CVE-2022-45796: SHARP Multifunction Printer - Command Injection

> Remote attackers can execute arbitrary commands on SHARP multifunction printers via the nw_interface.html component.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 16 Dec 2022
- **Updated:** 17 Apr 2025
- **Also known as:** GHSA-qwm8-3vw5-6956

## What is CVE-2022-45796?

CVE-2022-45796 is a critical command injection vulnerability in SHARP multifunction printers, published on 16 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Command injection vulnerability in nw_interface.html in SHARP multifunction printers (MFPs)'s Digital Full-color Multifunctional System 202 or earlier, 120 or earlier, 600 or earlier, 121 or earlier, 500 or earlier, 402 or earlier, 790 or earlier, and Digital Multifunctional System (Monochrome) 200 or earlier, 211 or earlier, 102 or earlier, 453 or earlier, 400 or earlier, 202 or earlier, 602 or earlier, 500 or earlier, 401 or earlier allows remote attackers to execute arbitrary commands via unspecified vectors.

Weakness: CWE-77 (Improper Neutralization of Special Elements used in a Command)

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

It affects 158 products.


Products: Sharp Bp-30c25 Firmware, Sharp Bp-30c25t Firmware, Sharp Bp-30c25y Firmware, Sharp Bp-30c25z Firmware, Sharp Bp-30m28 Firmware, Sharp Bp-30m28t Firmware, Sharp Bp-30m31 Firmware, Sharp Bp-30m31t Firmware, Sharp Bp-30m35 Firmware, Sharp Bp-30m35t Firmware, Sharp Bp-50c26 Firmware, Sharp Bp-50c31 Firmware, Sharp Bp-50c36 Firmware, Sharp Bp-50c45 Firmware, Sharp Bp-50c55 Firmware, Sharp Bp-50c65 Firmware, Sharp Bp-50m26 Firmware, Sharp Bp-50m31 Firmware, Sharp Bp-50m36 Firmware, Sharp Bp-50m45 Firmware and 138 more.

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

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

## Is CVE-2022-45796 being exploited?

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

## Other vulnerabilities in SHARP multifunction printers

- [CVE-2024-47406](https://insights.sbomify.com/CVE-2024-47406/): Auth bypass in Sharp Digital Full-color MFPs and Monochrome MFPs (critical 9.1)
- [CVE-2024-47005](https://insights.sbomify.com/CVE-2024-47005/): Missing authorization in Sharp Digital Full-color MFPs and Monochrome MFPs (high 8.1)
- [CVE-2024-42420](https://insights.sbomify.com/CVE-2024-42420/): Denial of service in Sharp Digital Full-color MFPs and Monochrome MFPs (high 7.5)
- [CVE-2024-43424](https://insights.sbomify.com/CVE-2024-43424/): Memory corruption in Sharp Digital Full-color MFPs and Monochrome MFPs (high 7.5)
- [CVE-2024-47549](https://insights.sbomify.com/CVE-2024-47549/): Cross-site scripting in Sharp Digital Full-color MFPs and Monochrome MFPs (high 7.4)

## Fix prompt for AI coding agents

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

What it is: CVE-2022-45796 is a critical command injection vulnerability in SHARP multifunction printers, published on 16 Dec 2022. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2022-45796 in the wild and no public exploit code.

Affected product: SHARP multifunction 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-45796/ (Markdown: https://insights.sbomify.com/CVE-2022-45796/index.md)
```

## Sources

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

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