# CVE-2025-60852: Code injection in n/a

> Attackers can execute arbitrary code by injecting malicious formulas into CSV exports generated by applications built with Instant Developer Foundation.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 23 Oct 2025
- **Updated:** 23 Oct 2025
- **Also known as:** GHSA-592w-453p-rpmg

## What is CVE-2025-60852?

CVE-2025-60852 is a medium-severity code injection vulnerability in n/a, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A CSV Injection vulnerability existed in Instant Developer Foundation versions prior to 25.0.9600. Applications built with affected versions of the framework did not properly sanitize user-controlled input before including it in CSV exports. This issue could lead to code execution on the system where the exported CSV file is opened.

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

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


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

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

## Is CVE-2025-60852 being exploited?

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

Public exploit code:

- This repository contains a Proof of Concept (PoC) for a CSV Injection (Formula Injection) vulnerability (CVE-2025-60852) affecting applications built with the Instant Developer Foundation framework (versions prior to 25.0). (github_poc): https://github.com/valeriocassoni/CSV-Injection-in-Instant-Developer-Foundation-25.0-PoC

## Fix prompt for AI coding agents

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

What it is: CVE-2025-60852 is a medium-severity code injection vulnerability in n/a, published on 23 Oct 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-60852 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-60852/ (Markdown: https://insights.sbomify.com/CVE-2025-60852/index.md)
```

## Sources

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

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