Skip to content
Server Security Center
KEVcritical10.0

CVE-2025-47812: Wing FTP Server Improper Neutralization of Null Byte or NUL Character

Wing FTP Server · listed in the CISA catalog of actively exploited vulnerabilities since 2025-07-14.

CVSS v3.1 (CVE record)
10.0
critical
EPSS (exploit probability, 30 days)
94%
higher than 99.8% of all CVEs
Added to CISA KEV
2025-07-14
US federal due date 2025-08-04
Automatable (CISA SSVC)
yes
technical impact: total

What is CVE-2025-47812?

In Wing FTP Server before 7.4.4. the user and admin web interfaces mishandle '\0' bytes, ultimately allowing injection of arbitrary Lua code into user session files. This can be used to execute arbitrary system commands with the privileges of the FTP service (root or SYSTEM by default).

This is thus a remote code execution vulnerability that guarantees a total server compromise. This is also exploitable via anonymous FTP accounts.

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: 2025-08-04 (passed) – a useful benchmark for everyone else, too.

CISA's assessment (SSVC)

Exploitation
Exploited in the wild
Automatable
Yes – attackers can automate it at scale
Technical impact
Total – full control of the component or total information disclosure

Weakness: CWE-158 Improper Neutralization of Null Byte or NUL Character

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.