CVE-2025-47812
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedIn 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceWing FTP Server before 7.4.4 improperly handles null bytes ('\0') in the user and admin web interfaces, allowing injection of arbitrary Lua code into user session files. This enables remote code execution with SYSTEM/root privileges, resulting in complete server compromise.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 7.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify Wing FTP Server is installedCheck for Wing FTP Server installation by looking for the executable or service. On Windows, check Program Files for 'Wing FTP Server' folder or look for the service named 'WingFTPService'. On Linux, check /opt/wingftp or similar installation directories.Affected if Wing FTP Server executable or service is found on the system
-
Determine installed versionAccess the admin web interface and check the version displayed on the login page or in the administration console, or check the WingFTPServer.xml or version.txt in the installation directory.Affected if The installed version number is less than 7.4.4
-
Confirm web interface is accessibleAttempt to reach the web interface on the configured port (typically 5466 for admin, 80/443 for user interface). Check HTTP/HTTPS response.Affected if The web interface responds and is accessible from the network
-
Check if anonymous FTP access is enabledIn the admin console, navigate to 'Users' and check if 'anonymous' user account exists and is enabled, or attempt anonymous FTP login to the server.Affected if Anonymous FTP account is enabled and allows login
The server is affected if Wing FTP Server is installed with a version lower than 7.4.4 and the web interface is accessible.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped7.4.4
Upgrade to Wing FTP Server 7.4.4 or later immediately. Until patched, disable anonymous FTP access and restrict web interface exposure to trusted networks only.
7.4.4
- 1. Download Wing FTP Server version 7.4.4 from the official vendor website (www.wftpserver.com)
- 2. Before upgrading, backup your current Wing FTP Server configuration and data directories
- 3. Stop the Wing FTP Server service
- 4. Install version 7.4.4 (or replace the existing installation files)
- 5. Start the Wing FTP Server service
- 6. Verify the upgrade was successful by checking the server version in the admin web interface
- 7. Review and test that all FTP, admin, and user web interface functionality is working correctly after upgrade
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation3.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,360.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47812 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47812 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data