CVE-2023-37879
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 · uneditedInsecure storage of sensitive information in Wing FTP Server (User Web Client) allows information elicitation.This issue affects Wing FTP Server: <= 7.2.0.
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 · moderate confidenceWing FTP Server versions 7.2.0 and below store sensitive information insecurely in the User Web Client component, allowing authenticated or unauthenticated attackers to elicitate this data. The vulnerability involves improper handling of credentials or personal data in storage.
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.2.0CVSS 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
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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 installationLocate the Wing FTP Server installation directory and locate the executable or service. Common locations include C:\Program Files\WingFTP Server or /opt/wingftpd/ on Linux. Check for the main executable (wingftpd.exe or wingftpd).Affected if Wing FTP Server is installed on the system
-
Determine installed versionOpen the Wing FTP Server administrative console (usually accessible via web browser on port 5466 by default) or check the software About/Help section. Alternatively, check the executable properties or the version.txt file in the installation directory.Affected if The installed version is 7.2.0 or any version below 7.2.0
-
Verify User Web Client is enabledLog into the Wing FTP Server administrative console and navigate to the Domain settings or Web Client settings. Check if the User Web Client interface is enabled and accessible (typically on port 80, 443, or 8080).Affected if The User Web Client is enabled and publicly or semi-publicly accessible
-
Check web client data storage locationsInspect the 'webclient' or 'www' subdirectory within the Wing FTP Server installation folder. Look for configuration files, session files, or data storage that may contain credentials or personal user information stored in plain text or with weak protection.Affected if Sensitive credentials or personal data are found stored without adequate encryption in the web client data directory
-
Assess network exposureVerify which network interfaces and IP addresses the web client is bound to. Check firewall rules and port listeners to determine if the web client port is exposed to untrusted networks or the internet.Affected if The User Web Client is accessible from untrusted networks or the internet without proper access controls
A system is affected if Wing FTP Server version 7.2.0 or below is installed AND the User Web Client component is enabled and accessible, with sensitive data stored in insecure locations accessible to attackers.
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 · scopedUpgrade Wing FTP Server to a version newer than 7.2.0. If upgrading is not immediately possible, review and harden file/database permissions on the server and ensure the web client is not exposed to untrusted networks.
Version 7.2.1 or later (verify exact fixed release on vendor website)
- 1. Check the current Wing FTP Server version by accessing the administration console
- 2. Navigate to the vendor website (www.wftpserver.com) to identify the latest stable release that addresses CVE-2023-37879
- 3. Review the release notes or changelog for version 7.2.1 or later to confirm the security fix for CWE-922 (Insecure Storage of Sensitive Information)
- 4. Create a full backup of the Wing FTP Server configuration, user data, and settings
- 5. Schedule a maintenance window for the upgrade
- 6. Download the latest version from the official vendor website
- 7. Stop the Wing FTP Server service before upgrading
- 8. Install the updated version following the vendor's upgrade documentation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation6.0 h
- Implementation12.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,968.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-37879 — 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-2023-37879 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