# CVE-2025-59711: Path traversal in n/a

> An authenticated attacker can write files outside the destination directory or coerce service authentication via a directory traversal vulnerability in Biztalk360.

- **Severity:** High 8.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:L`)
- **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:** 3 Apr 2026
- **Updated:** 3 Apr 2026
- **Also known as:** GHSA-q6cm-wqcq-7q3c

## What is CVE-2025-59711?

CVE-2025-59711 is a high-severity path traversal vulnerability in n/a, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

An issue was discovered in Biztalk360 before 11.5. Because of mishandling of user-provided input in an upload mechanism, an authenticated attacker is able to write files outside of the destination directory and/or coerce an authentication from the service, aka Directory Traversal.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

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

It affects 1 product.


Products: Kovai Biztalk360.

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

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

## Is CVE-2025-59711 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2025-59710](https://insights.sbomify.com/CVE-2025-59710/): File upload in n/a (high 8.8)
- [CVE-2025-59709](https://insights.sbomify.com/CVE-2025-59709/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-59711 is a high-severity path traversal vulnerability in n/a, published on 3 Apr 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-59711 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-59711/ (Markdown: https://insights.sbomify.com/CVE-2025-59711/index.md)
```

## Sources

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

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