# CVE-2025-41439: Cross-site scripting in RICOH Streamline NX

> Reflected XSS in RICOH Streamline NX allows attackers to execute arbitrary scripts in users' browsers via a specific parameter.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA: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:** 30 Jun 2025
- **Updated:** 30 Jun 2025
- **Also known as:** GHSA-5r8q-4qq6-rjv8

## What is CVE-2025-41439?

CVE-2025-41439 is a medium-severity cross-site scripting vulnerability in RICOH Streamline NX, published on 30 Jun 2025. 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

A reflected cross-site scripting vulnerability via a specific parameter exists in SLNX Help Documentation of RICOH Streamline NX. If this vulnerability is exploited, an arbitrary script may be executed in the web browser of the user who accessed the product.

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

## Which versions are affected by CVE-2025-41439?


## How do I fix CVE-2025-41439?

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

## Is CVE-2025-41439 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-41439 and fix it if it is affected.

What it is: CVE-2025-41439 is a medium-severity cross-site scripting vulnerability in RICOH Streamline NX, published on 30 Jun 2025. 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-2025-41439 in the wild and no public exploit code.

Affected product: RICOH Streamline NX. 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-2025-41439/ (Markdown: https://insights.sbomify.com/CVE-2025-41439/index.md)
```

## Sources

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

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