Security readout for executives and security teams
Plain-English summary
QuickShare File Server 1.2.1 can let a logged-in FTP user escape their assigned folder. If write access is enabled, they may place files in sensitive Windows locations, creating a route to remote code execution.
Executive priority
Prioritize remediation for any reachable deployment because the impact is full host compromise after authenticated access. If the product is no longer business-critical, decommissioning is likely lower risk than preserving a legacy FTP service.
Technical view
The FTP service improperly sanitizes user-supplied paths, enabling CWE-22 path traversal. Authenticated users can read or write outside the virtual directory. With the default Writable account option enabled, file placement in privileged locations can lead to code execution.
Likely exposure
Exposure is likely limited to legacy QuickShare File Server 1.2.1 deployments, especially Windows hosts exposing FTP to users, partners, or the internet. Source version metadata is sparse, so CPE-only inventory may miss it.
Exploitation context
Public exploit references exist, including Metasploit and Exploit-DB entries. The supplied bundle does not show CISA KEV listing or confirmed active exploitation, so treat weaponization as public but active exploitation as unproven here.
Researcher notes
The CVE record was published in 2025 for a 2011 product issue. The bundle names QuickShare File Server 1.2.1, but affected CPE/version data is incomplete, so validation should combine asset discovery, configuration review, and service exposure checks.
Mitigation direction
- Identify and remove any exposed QuickShare File Server 1.2.1 instances.
- Upgrade to the vendor-released 1.2.2 patch where applicable.
- Disable Writable access for accounts unless explicitly required.
- Restrict FTP access to trusted networks or VPN paths.
- Decommission unsupported QuickShare deployments if patching is not viable.
Validation and detection
- Inventory hosts for QuickShare File Server and confirm exact version.
- Review FTP account settings for Writable access.
- Check whether the FTP service is reachable externally.
- Inspect sensitive directories for unexpected uploaded files.
- Review logs for authenticated traversal-like file access patterns.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-22: File access and web shell behavior lookup
File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupExecution behavior lookup
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupFile access behavior lookup
The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2011-10010 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Critical
- CVSS
- 9.4 (4.0)
- Known Exploited
- No
- Published
Vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H——VulnCheckVulnerability scoring details
Base CVSS 4.0 score
9.4CriticalVector: CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://raw.githubusercontent.com/rapid7/metasploit-framework/master/modules/exploits/windows/ftp/quickshare_traversal_write.rbCVE reference, VulnCheck · exploit
- https://www.exploit-db.com/exploits/16105CVE reference, VulnCheck · exploit
- https://www.exploit-db.com/exploits/18933CVE reference, VulnCheck · exploit
- https://web.archive.org/web/20110814125645/http://www.digital-echidna.org/2011/02/quickshare-file-share-1-2-1-directory-traversal-vulnerability/CVE reference, VulnCheck · technical-description, exploit
- https://web.archive.org/web/20120125101026/http://www.quicksharehq.com/blog/quickshare-file-server-1-2-2-released.htmlCVE reference, VulnCheck · vendor-advisory, patch
- https://www.vulncheck.com/advisories/quickshare-file-server-path-traversal-rceCVE reference, VulnCheck · third-party-advisory
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.