# CVE-2024-47549: Cross-site scripting in Sharp Digital Full-color MFPs and Monochrome MFPs

> Attackers can execute malicious scripts in browsers via crafted URLs targeting Sharp and Toshiba multifunction printers.

- **Severity:** High 7.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 25 Oct 2024
- **Updated:** 25 Oct 2024
- **Also known as:** GHSA-hfvw-6r46-qm8f

## What is CVE-2024-47549?

CVE-2024-47549 is a high-severity cross-site scripting vulnerability in Sharp Digital Full-color MFPs and Monochrome MFPs, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Sharp and Toshiba Tec MFPs improperly process query parameters in HTTP requests, which may allow contamination of unintended data to HTTP response headers.
Accessing a crafted URL which points to an affected product may cause malicious script executed on the web browser.

Weakness: CWE-116 (Improper Encoding or Escaping of Output), CWE-644 (Improper Neutralization of HTTP Headers for Scripting Syntax)

## Which versions are affected by CVE-2024-47549?

It affects 320 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 300 more.

## How do I fix CVE-2024-47549?

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

## Is CVE-2024-47549 being exploited?

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

## Other vulnerabilities in Sharp Digital Full-color MFPs and Monochrome MFPs

- [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-2022-45796](https://insights.sbomify.com/CVE-2022-45796/): SHARP Multifunction Printer - Command Injection (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)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-47549 and fix it if it is affected.

What it is: CVE-2024-47549 is a high-severity cross-site scripting vulnerability in Sharp Digital Full-color MFPs and Monochrome MFPs, published on 25 Oct 2024. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-47549 in the wild and no public exploit code.

Affected product: Sharp Digital Full-color MFPs and Monochrome MFPs. 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-2024-47549/ (Markdown: https://insights.sbomify.com/CVE-2024-47549/index.md)
```

## Sources

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

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