Skip to content
Server Security Center
KEVmedium4.3

CVE-2025-47813: Wing FTP Server Information Disclosure

Wing FTP Server · listed in the CISA catalog of actively exploited vulnerabilities since 2026-03-16.

CVSS v3.1 (CVE record)
4.3
medium
EPSS (exploit probability, 30 days)
63%
higher than 99.2% of all CVEs
Added to CISA KEV
2026-03-16
US federal due date 2026-03-30
Automatable (CISA SSVC)
no
technical impact: total

CVE-2025-47813 explained

CVE-2025-47813 is an information disclosure flaw in Wing FTP Server before 7.4.4. The loginok.html page reveals the full local installation path of the application when it receives a long value in the UID cookie. CISA lists it as known to be exploited, so affected servers should be updated promptly.

Impact

An attacker with low privileges can reach the flaw over the network, with low complexity and no user interaction, and learn the server's local installation path. The CVSS rating shows a limited confidentiality impact and no integrity or availability impact. CISA's SSVC rates technical impact as total and automatable as no. CISA reports active exploitation; ransomware use is unknown.

Who is affected

The CVE record lists wftpserver Wing FTP Server versions < 7.4.4 as affected, meaning all versions before 7.4.4. The fix is included in version 7.4.4. The version data comes from the CVE record as published by its CNA (mitre).

Written with AI from the data on this page and checked against it automatically.

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.

CISA required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

CISA notes

Affected and fixed versions

From the CVE record published by the vendor or CVE numbering authority.

  • wftpserver Wing FTP Server
    Affected
    • < 7.4.4
    Fixed in
    • 7.4.4

How to fix it

  • Update to a fixed version: 7.4.4.
  • Vendor advisory: wftpserver.com
  • CISA's deadline for US federal agencies: 2026-03-30 (passed) – a useful benchmark for everyone else, too.

What to do

  1. Update Wing FTP Server to version 7.4.4 or later.
  2. Apply any mitigations in the vendor advisory if you cannot update immediately.
  3. Limit network access to the Wing FTP Server web interface to trusted users and networks.
  4. Review server logs for unusual requests to loginok.html or abnormally long UID cookie values.
  5. For cloud deployments, follow applicable BOD 22-01 guidance as stated in CISA's required action.

Written with AI from the data on this page and checked against it automatically.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
No – each attack needs manual steps
Technical impact
Total – full control of the component or total information disclosure

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

Questions about CVE-2025-47813

Which version fixes CVE-2025-47813?
The CVE record names Wing FTP Server 7.4.4 as the fixed version. All versions before 7.4.4 are affected.
Is this vulnerability being exploited?
Yes. CISA added CVE-2025-47813 to its Known Exploited Vulnerabilities catalog on 2026-03-16, with a US federal due date of 2026-03-30. Whether it is used in ransomware campaigns is unknown.
Why act on a medium-severity information leak?
Attackers are known to exploit it, and CISA rates its technical impact as total. Disclosing the installation path gives attackers information about the server. CISA requires applying vendor mitigations or discontinuing use if mitigations are unavailable.

Written with AI from the data on this page and checked against it automatically.

References

Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-21. Always confirm with the vendor's or distribution's advisory before patching.