# CVE-2025-47813: Wing FTP Server Information Disclosure

> An attacker can obtain the full local installation path of Wing FTP Server by sending a long UID cookie value, potentially aiding further attacks.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Yes, since 16 Mar 2026 (CISA KEV)
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Jul 2025
- **Updated:** 17 Mar 2026
- **Also known as:** GHSA-2vvg-j984-hh8p

## What is CVE-2025-47813?

CVE-2025-47813 is a medium-severity vulnerability in wftpserver Wing FTP Server, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

loginok.html in Wing FTP Server before 7.4.4 discloses the full local installation path of the application when using a long value in the UID cookie.

Weakness: CWE-209 (Generation of Error Message Containing Sensitive Information)

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

It affects 1 product.


Products: Wftpserver Wing Ftp Server.

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

No fix has been published for CVE-2025-47813 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 30 Mar 2026.

## Is CVE-2025-47813 being exploited?

Yes. Attackers have exploited CVE-2025-47813 in the wild since at least 16 Mar 2026.

Public exploit code:

- Wing FTP Server <= 7.4.3 - Path Disclosure via Overlong UID Cookie (nuclei): http/cves/2025/CVE-2025-47813.yaml

## Other vulnerabilities in wftpserver Wing FTP Server

- [CVE-2025-47812](https://insights.sbomify.com/CVE-2025-47812/): Wing FTP Server Improper Neutralization of Null Byte or NUL Character (critical 10.0, exploited in the wild)
- [CVE-2026-44403](https://insights.sbomify.com/CVE-2026-44403/): Wing FTP Server < 8.1.3 Authenticated Remote Code Execution via Session Serialization (high 8.6)
- [CVE-2020-37032](https://insights.sbomify.com/CVE-2020-37032/): Wing FTP Server 6.3.8 - Remote Code Execution (high 8.6)
- [CVE-2019-25267](https://insights.sbomify.com/CVE-2019-25267/): Wing FTP Server 6.0.7 - Unquoted Service Path (high 8.5)
- [CVE-2020-9470](https://insights.sbomify.com/CVE-2020-9470/): Information disclosure in n/a (high 7.8)

## Fix prompt for AI coding agents

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

What it is: CVE-2025-47813 is a medium-severity vulnerability in wftpserver Wing FTP Server, published on 10 Jul 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: Yes. Attackers have exploited CVE-2025-47813 in the wild since at least 16 Mar 2026.

Affected product: wftpserver Wing FTP Server. 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-47813/ (Markdown: https://insights.sbomify.com/CVE-2025-47813/index.md)
```

## Sources

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

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