# CVE-2025-1421: Formula injection in a CSV file in Proget MDM

> Attackers can inject malicious formulas into CSV exports, leading to remote code execution on victims' PCs when opening the file in spreadsheet applications.

- **Severity:** Low 2.4 (`CVSS:4.0/AV:A/AC:L/AT:N/PR:H/UI:A/VC:N/VI:N/VA:N/SC:L/SI:L/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 May 2025
- **Updated:** 21 May 2025
- **Also known as:** GHSA-g45p-2vh4-m46h

## What is CVE-2025-1421?

CVE-2025-1421 is a low-severity code injection vulnerability in Proget, published on 21 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Data provided in a request performed to the server while activating a new device are put in a database. Other high privileged users might download this data as a CSV file and corrupt their PC by opening it in a tool such as Microsoft Excel. The attacker could gain remote access to the user's PC.

This issue has been fixed in 2.17.5 version of Konsola Proget (server part of the MDM suite).

Weakness: CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

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

## Is CVE-2025-1421 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1421 is a low-severity code injection vulnerability in Proget, published on 21 May 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2025-1421 in the wild and no public exploit code.

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

## Sources

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

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