Security readout for executives and security teams
Plain-English summary
ProjectSend r582 is reported to allow SQL injection through several web request parameters. In business terms, a vulnerable file-sharing portal could let an attacker interfere with the application database. The supplied sources do not provide severity scoring, authentication requirements, or a named fixed version.
Executive priority
Treat as a targeted review item. Escalate to urgent remediation if ProjectSend r582 is internet-facing or stores sensitive files, because SQL injection can affect database confidentiality and integrity.
Technical view
CVE-2016-10731 describes SQL injection in ProjectSend, formerly cFTP, r582 across parameters in manage-files.php, clients.php, process-zip-download.php, and home-log.php. The CVE record lists no CVSS, CWE, CPE, vendor advisory, or remediation details in the supplied bundle.
Likely exposure
Exposure is most likely limited to organizations running ProjectSend/cFTP r582. The sources do not state whether affected routes require authentication, whether later versions are affected, or whether internet exposure is common.
Exploitation context
The source bundle says this CVE is not in KEV and provides no cited evidence of active exploitation. A public GitHub reference exists, so defenders should assume technical details may be publicly accessible.
Researcher notes
Evidence is sparse: the CVE description names affected parameters and version r582, but supplied metadata lacks CVSS, CWE, CPE, authentication context, exploit status, and fixed-version guidance. Avoid broader product claims without additional vendor evidence.
Mitigation direction
- Inventory any ProjectSend or cFTP deployments and identify installed versions.
- Check ProjectSend or vendor guidance for patched versions or official remediation.
- Restrict access to the application to trusted users and networks where feasible.
- Prioritize remediation for internet-facing or sensitive file-sharing deployments.
- Monitor database and web logs for unusual activity around the named PHP routes.
Validation and detection
- Confirm whether ProjectSend/cFTP r582 exists in asset inventory.
- Review application version evidence from deployment records or administrative interfaces.
- Check access logs for requests to the affected PHP endpoints.
- Verify whether any compensating access controls limit access to the application.
- Document uncertainty where authentication requirements or patch status cannot be proven.
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.
Database behavior lookup
The CVE wording references database injection or access, so collection and exfiltration review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
Open ATT&CK lookupCVE-2016-10731 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
- Unknown
- CVSS
- Not scored
- Known Exploited
- No
- Published
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.
CVSS and timeline data
No CVSS vectors or timeline events were available in the normalized CVE source material.
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/sandboxescape/ProjectSend-multiple-vulnerabilities/CVE reference · x_refsource_MISC
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.
