# CVE-2022-37406: Cross-site scripting in Aficio SP 4210N

> An authenticated administrator can inject arbitrary scripts into the Ricoh Aficio SP 4210N printer firmware, potentially compromising the device.

- **Severity:** Medium 4.8 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 7 Dec 2022
- **Updated:** 23 Apr 2025
- **Also known as:** GHSA-2v8x-7464-c2fx

## What is CVE-2022-37406?

CVE-2022-37406 is a medium-severity cross-site scripting vulnerability in RICOH COMPANY, LTD. Aficio SP 4210N, published on 7 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting vulnerability in Aficio SP 4210N firmware versions prior to Web Support 1.05 allows a remote authenticated attacker with an administrative privilege to inject an arbitrary script.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Ricoh Aficio Sp 4210n Firmware.

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

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

## Is CVE-2022-37406 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2022-37406 is a medium-severity cross-site scripting vulnerability in RICOH COMPANY, LTD. Aficio SP 4210N, published on 7 Dec 2022. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2022-37406 in the wild and no public exploit code.

Affected product: RICOH COMPANY, LTD. Aficio SP 4210N. 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-37406/ (Markdown: https://insights.sbomify.com/CVE-2022-37406/index.md)
```

## Sources

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

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