# CVE-2025-26260: Plenti - Code Injection - Denial of Services

> Attackers can execute arbitrary code by uploading maliciously named Svelte files via the postLocal endpoint in Plenti.

- **Severity:** High 8.8 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **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:** Yes
- **Published:** 12 Mar 2025
- **Updated:** 19 Mar 2025
- **Also known as:** GHSA-mj4v-hp69-27x5, GO-2025-3454, GO-2025-3515

## What is CVE-2025-26260?

CVE-2025-26260 is a high-severity code injection vulnerability in n/a, published on 12 Mar 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

Plenti <= 0.7.16 is vulnerable to code execution. Users uploading '.svelte' files with the /postLocal endpoint can define the file name as javascript codes. The server executes the uploaded file name in host, and cause code execution.

Weakness: CWE-94 (Improper Control of Generation of Code)

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

4 open source packages ship an affected version, including github.com/plentico/plenti. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/plentico/plenti` | Go | All versions | None |
| `github.com/plentico/plenti` | Go | All versions | 0.7.17 |
| `github.com/plentico/plenti` | Go | All versions | 0.7.17 |
| `github.com/plentico/plenti` | Go | All versions | 0.7.17 |

Products: Plenti Plenti.

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

Upgrade github.com/plentico/plenti to 0.7.17 or later.

## Is CVE-2025-26260 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2024-49380](https://insights.sbomify.com/CVE-2024-49380/): Plenti arbitrary file write vulnerability (high 8.9)
- [CVE-2024-49381](https://insights.sbomify.com/CVE-2024-49381/): Plenti arbitrary file deletion vulnerability (high 7.7)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-26260 is a high-severity code injection vulnerability in n/a, published on 12 Mar 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-26260 exists.

Affected packages and fixed versions:
- github.com/plentico/plenti (Go): affected all versions; no fix listed
- github.com/plentico/plenti (Go): affected all versions; fixed in 0.7.17
- github.com/plentico/plenti (Go): affected all versions; fixed in 0.7.17
- github.com/plentico/plenti (Go): affected all versions; fixed in 0.7.17

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-26260/ (Markdown: https://insights.sbomify.com/CVE-2025-26260/index.md)
```

## Sources

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

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