CVE-2026-44403
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 · uneditedWing FTP Server before 8.1.3 contains an authenticated remote code execution vulnerability in the session serialization mechanism that allows authenticated administrators to inject arbitrary Lua code through the domain admin mydirectory field. Attackers can exploit unsafe serialization of session values into Lua source code without proper escaping of closing delimiters, causing the injected code to be executed when the poisoned session is loaded via loadfile().
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 8.1.3 allows authenticated administrators to inject arbitrary Lua code through the domain admin 'mydirectory' field. The vulnerability stems from unsafe serialization of session values directly into Lua source code without escaping closing delimiters, causing injected code to execute when the poisoned session is loaded via loadfile().
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< 8.1.3CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/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.
-
Identify Wing FTP Server installation and versionCheck the installed Wing FTP Server version - this is typically visible in the server admin console, in the Windows Services list, or in the program's About/Help section. Compare the version number to the affected range (versions before 8.1.3).Affected if The installed version is Wing FTP Server and the version is lower than 8.1.3
-
Verify administrative access is enabledConfirm whether remote or local administrator accounts exist and are enabled for Wing FTP Server. Check if the web admin interface or console is accessible.Affected if Administrative accounts exist and the admin interface is accessible (even to trusted users, the vulnerability applies if admin access exists)
-
Check domain admin configuration accessExamine whether domain-level administrative accounts can be configured or if any domain admin functionality exists in the installation.Affected if Domain admin accounts or the domain admin 'mydirectory' feature is available in the installation
-
Inspect session storage for Lua code injection artifactsIf accessible, examine Wing FTP Server session files or configuration files for unexpected Lua code patterns, particularly any loadfile() calls or suspicious string literals that may indicate prior exploitation.Affected if Session files or configuration contain unescaped Lua delimiters or unexpected Lua source code that could indicate injection
You are affected if Wing FTP Server version is below 8.1.3 and administrative or domain admin access exists in your environment.
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 · scoped8.1.3
Upgrade to Wing FTP Server 8.1.3 or later. Until then, limit administrative access to trusted personnel only and monitor for suspicious admin session activity.
8.1.3
- 1. Back up the current Wing FTP Server configuration and data directories
- 2. Download Wing FTP Server version 8.1.3 from the official vendor website (www.wftpserver.com)
- 3. Stop the Wing FTP Server service before upgrading
- 4. Install version 8.1.3 following the vendor's standard upgrade procedure
- 5. Verify the upgrade was successful by checking the server version in the admin console
- 6. Restart the Wing FTP Server service
- 7. Test that administrator authentication works correctly and that the vulnerability is remediated
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation4.0 h
- Testing3.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,408.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-44403 — 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-2026-44403 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