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

> Attackers can execute arbitrary code by crafting inputs that trigger code execution when exported CSV files are opened in compatible applications.

- **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:** No
- **Published:** 31 Jul 2025
- **Updated:** 5 Jul 2026
- **Also known as:** GHSA-wc34-p4fh-wr9q

## What is CVE-2025-50572?

CVE-2025-50572 is a high-severity code injection vulnerability in n/a, published on 31 Jul 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

Archer 6.11.00204.10014 allows attackers to execute arbitrary code via crafted system inputs that would be exported into the CSV and be executed after the user opened the file with compatible applications. NOTE: the Supplier does not accept this as a valid vulnerability report against their product.

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

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


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

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

## Is CVE-2025-50572 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-50572 is a high-severity code injection vulnerability in n/a, published on 31 Jul 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-50572 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-50572/ (Markdown: https://insights.sbomify.com/CVE-2025-50572/index.md)
```

## Sources

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

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