# CVE-2025-7619: WellChoose｜BatchSignCS - Arbitrary File Write through Path Traversal

> Remote attackers can write arbitrary files to any path via a malicious website, potentially leading to arbitrary code execution in BatchSignCS.

- **Severity:** High 8.7 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/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:** 14 Jul 2025
- **Updated:** 14 Jul 2025
- **Also known as:** GHSA-2jx4-mmr5-ww75

## What is CVE-2025-7619?

CVE-2025-7619 is a high-severity path traversal vulnerability in WellChoose BatchSignCS, published on 14 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

BatchSignCS, a background Windows application developed by WellChoose, has an Arbitrary File Write vulnerability. If a user visits a malicious website while the application is running, remote attackers can write arbitrary files to any path and potentially lead to arbitrary code execution.

Weakness: CWE-23 (Relative Path Traversal)

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


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

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

## Is CVE-2025-7619 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-7619 is a high-severity path traversal vulnerability in WellChoose BatchSignCS, published on 14 Jul 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-7619 in the wild and no public exploit code.

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

## Sources

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

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