CVE-2025-47812 — Wing FTP Server Improper Neutralization of Null Byte or NUL Character Vulnerability
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.
Who exploits it and how urgent it is
A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.
How the score was calculated
- Confirmed exploitation (CISA KEV)+35
- Public exploit/PoC (nuclei, metasploit, exploitdb, github)+20
- EPSS 93.9% (30-day exploitation probability)+15
- Technical severity (critical)+10
- Automatable exploitation (SSVC)+3
The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).
Triage
Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.
CISA SSVC assessment CISA
Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.
Remediation
Fixes and mitigations documented by the sources — linked to the original advisory.
- Documented mitigation — www.vicarius.io (NIST National Vulnerability Database)
CISA required action CISA
Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
US federal deadline: Aug 4, 2025 — passed 438 day(s) ago
First 24 hours
Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.
- Identify exposed assets running the affected vendor/product/version combinations (Wftpserver Wing Ftp Server).
- Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
- The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
- Apply the documented mitigations until a definitive fix is available.
- EPSS ahead of 100% of scored CVEs: prioritize it in the patch queue.
- Search available logs for exploit probes, errors and authentication anomalies.
Affected scope
Vendor, product and versions as the sources word them.
| Vendor | Product | Versions | Status | Source |
|---|---|---|---|---|
| Wftpserver | Wing Ftp Server | < 7.4.4 | Vulnerable | CVE Program (cve.org) e CISA ADP |
| Wftpserver | Wing Ftp Server | < 7.4.4 | Vulnerable | NIST National Vulnerability Database |
Attack characteristics
The CVSS vector, decoded. It describes the attack, not your exposure to it.
Every base score collected
Sources score independently and may disagree; each row says who scored it and under which version.
| Score | Version | Severity | Expl. | Impact | Scored by |
|---|---|---|---|---|---|
| 10.0 | CVSS 3.1 | Critical | 3.9 | 6.0 | cve@mitre.org via NIST National Vulnerability Database |
| 10.0 | CVSS 3.1 | Critical | — | — | GitHub, Inc. via GitHub Security Advisories |
| 10.0 | CVSS 3.1 | Critical | — | — | mitre via CVE Program (cve.org) e CISA ADP |
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H (score shown at the top: cve@mitre.org) Weakness MITRE
Weakness class according to MITRE’s CWE catalog.
CISA KEV details CISA
CISA lists a CVE once it has evidence of exploitation against real targets.
CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a reference date.
Public exploits, PoCs and detection templates
Public code that demonstrates or tests the flaw raises the odds of mass exploitation — and Nuclei templates help find vulnerable assets in your environment.
- Wing FTP Server Authenticated Command Execution excellent Jun 19, 2014
- Wing FTP Server NULL-byte Authentication Bypass (CVE-2025-47812) excellent Jun 30, 2025
- Wing FTP Server Remote Code Execution (RCE) Exploit (CVE-2025-47812) ★ 54 Jul 1, 2025
- Simple exploit for Wing FTP Server RCE (CVE-2025-47812) to run commands and get a reverse shell. For educational use only. ★ 13 Jul 1, 2025
- Wing FTP Server RCE via Lua Injection ★ 3 Jul 2, 2025
- r0otk3r/CVE-2025-47812 ★ 2 Jul 27, 2025
- CVE-2025-47812 POC ★ 2 Feb 17, 2026
- Unauthenticated remote code execution vulnerability in Wing FTP Server <= 7.4.3. ★ 2 Feb 19, 2026
- blindma1den/CVE-2025-47812 ★ 1 Jul 17, 2025
- 0xjuarez/CVE-2025-47812 ★ 1 Feb 24, 2026
- Majdae/CVE-2025-47812-Research ★ 1 Apr 9, 2026
- Remote Command Execution exploit for Wing FTP Server (CVE-2025-47812) ★ 0 Jul 4, 2025
Warning: public PoCs are sometimes disguised malware. Use them only for authorized testing in an isolated environment. This portal does not host exploit code — it only points to the sources.
EPSS over time FIRST
Oct 12, 2026 → Oct 15, 2026 · 4 reading(s) · max 93.88%
Detection
Read off the CVSS vector and the weakness class. Starting points, not tested rules.
- Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
- Hunt retroactively in logs from before Jul 14, 2025 (KEV listing): exploitation may have started earlier.
Timeline
What happened to this CVE, newest first.
- 2026
- Fix documented
- Affected products added · wftpserver/wing ftp server
- Source status changed · Published → Analyzed
- Record published
- Affected products added · wftpserver/wing ftp server
- CVSS changed · 10.0
- Source status changed · → Published
- SSVC assessment updated
- Added to CISA KEV (detected)
- Record created in this database
- 2025
- Added to CISA KEV catalog
- CVE published
Source activity
Repeated readings are counted rather than listed.
- 3× References added · Oct 13, 2026 – Oct 13, 2026
- 1× Official description updated · Oct 13, 2026 – Oct 13, 2026
References
9 on the record
- www.vicarius.io/vsociety/posts/cve-2025-47812-mitigation-script-remote-code-execution
- www.cisa.gov/known-exploited-vulnerabilities-catalog
- nvd.nist.gov/vuln/detail/CVE-2025-47812
- www.vicarius.io/vsociety/posts/cve-2025-47812-detection-script-remote-code-execution-
- www.huntress.com/blog/wing-ftp-server-remote-code-execution-cve-2025-47812-exploited-i
- www.rcesecurity.com/2025/06/what-the-null-wing-ftp-server-rce-cve-2025-47812
- github.com/advisories/GHSA-j4xf-75rr-vvrv
- www.wftpserver.com
- www.rcesecurity.com/2025/06/what-the-null-wing-ftp-server-rce-cve-2025-47812/
Elsewhere on this site
Related CVEs (same products)
- High CVE-2026-44403 Wing FTP Server < 8.1.3 Authenticated Remote Code Execution via Session Serialization May 12, 2026
- Low CVE-2020-37079 Wing FTP Server < 6.2.7 - Cross-site Request Forgery Feb 6, 2026
- High CVE-2019-25267 Wing FTP Server 6.0.7 - Unquoted Service Path Feb 4, 2026
- High CVE-2020-37032 Wing FTP Server 6.3.8 - Remote Code Execution Jan 30, 2026
- Medium CVE-2025-47813 Wing FTP Server Information Disclosure Vulnerability KEV Jul 10, 2025
Not in any source we poll
Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.
- No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
- No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
- No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record
Text assembled only from the fields above — no additional claims.
What should defenders know first?
CVE-2025-47812 is "Wing FTP Server Improper Neutralization of Null Byte or NUL Character Vulnerability", rated Critical. It affects Wing Ftp Server (Wftpserver); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 10.0 describes technical severity. EPSS 93.88% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.
Comments
Moderated technical discussion. Read the community guidelines.
No comments yet.
Sign in or create an account to comment and suggest corrections.