# CVE-2025-11655: Total.js Flow SVG File unrestricted upload

> Remote attackers can upload malicious SVG files to Total.js Flow, potentially leading to code execution due to unrestricted file upload vulnerabilities.

- **Severity:** Medium 5.1 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 13 Oct 2025
- **Updated:** 14 Oct 2025
- **Also known as:** GHSA-7gx8-8jq4-q6j2

## What is CVE-2025-11655?

CVE-2025-11655 is a medium-severity vulnerability in Total.js Flow, published on 13 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

A security flaw has been discovered in Total.js Flow up to 673ef9144dd25d4f4fd4fdfda5af27f230198924. The impacted element is an unknown function of the component SVG File Handler. Performing manipulation results in unrestricted upload. The attack can be initiated remotely. The exploit has been released to the public and may be exploited. Continious delivery with rolling releases is used by this product. Therefore, no version details of affected nor updated releases are available. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-434 (Unrestricted Upload of File with Dangerous Type), CWE-284 (Improper Access Control)

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


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

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

## Is CVE-2025-11655 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-11655 is a medium-severity vulnerability in Total.js Flow, published on 13 Oct 2025. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-11655 in the wild and no public exploit code.

Affected product: Total.js Flow. 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-11655/ (Markdown: https://insights.sbomify.com/CVE-2025-11655/index.md)
```

## Sources

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

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