# CVE-2025-1836: Incorta Edit Insight csv injection

> Remote attackers can inject malicious CSV content via the Service Name argument in Incorta's Edit Insight Handler, potentially corrupting data exports.

- **Severity:** Medium 5.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:L/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 2 Mar 2025
- **Updated:** 3 Mar 2025
- **Also known as:** GHSA-x99v-9xq5-53jh

## What is CVE-2025-1836?

CVE-2025-1836 is a medium-severity vulnerability in Incorta, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

A vulnerability was found in Incorta 2023.4.3. It has been classified as problematic. Affected is an unknown function of the component Edit Insight Handler. The manipulation of the argument Service Name leads to csv injection. It is possible to launch the attack remotely. The vendor was contacted early about this disclosure but did not respond in any way.

Weakness: CWE-74 (Improper Neutralization of Special Elements in Output Used by a Downstream Component), CWE-1236 (Improper Neutralization of Formula Elements in a CSV File)

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


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

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

## Is CVE-2025-1836 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-1836 is a medium-severity vulnerability in Incorta, published on 2 Mar 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-1836 in the wild and no public exploit code.

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

## Sources

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

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