# CVE-2025-70842: Cross-site scripting in n/a

> An authenticated administrator can upload malicious SVG files to execute JavaScript in the browsers of other users, including unauthenticated visitors.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 12 May 2026
- **Updated:** 12 May 2026
- **Also known as:** GHSA-7m9c-h5vv-88gq

## What is CVE-2025-70842?

CVE-2025-70842 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

A Stored Cross-Site Scripting (XSS) vulnerability was discovered in the File Management module of FluentCMS 1.2.3. The flaw allows an authenticated administrator to upload crafted SVG files containing malicious JavaScript code. Once uploaded, the script executes in the browser of any user who accesses the direct URL of the image, including unauthenticated visitors.

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

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


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

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

## Is CVE-2025-70842 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70842 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2025-70842 is a medium-severity cross-site scripting vulnerability in n/a, published on 12 May 2026. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-70842 exists.

Affected product: n/a. 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-70842/ (Markdown: https://insights.sbomify.com/CVE-2025-70842/index.md)
```

## Sources

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

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