Security readout for executives and security teams
Plain-English summary
CVE-2016-10734 describes an authorization weakness in ProjectSend, formerly cFTP, release r582. A log export endpoint may let a user access data by referencing an object they should not control. Business impact depends on what logs contain and whether the affected endpoint is reachable.
Executive priority
Prioritize if ProjectSend/cFTP r582 is internet-facing or stores sensitive client, user, or operational logs. If the product is not used, no action is required beyond documenting non-exposure.
Technical view
The CVE states that ProjectSend/cFTP r582 has an Insecure Direct Object Reference in includes/actions.log.export.php. The public record does not provide CVSS, CWE mapping, affected CPEs, exploit details, or a fixed version. Treat this as a targeted authorization review item for legacy ProjectSend deployments.
Likely exposure
Exposure is most likely in organizations running ProjectSend/cFTP r582 with the log export PHP endpoint present and accessible. The source bundle does not identify other affected versions or products, so broader exposure should not be assumed without vendor or project confirmation.
Exploitation context
The source bundle does not cite active exploitation, and the CVE is not marked as CISA KEV. Public evidence is limited to the CVE description and a referenced GitHub vulnerability report, so exploitation status should be considered unconfirmed.
Researcher notes
Evidence is sparse. The CVE gives only the affected release and endpoint, with no CVSS, CWE, CPE, patch, or exploitation confirmation. Validate impact in a controlled environment without publishing exploit details.
Mitigation direction
- Inventory ProjectSend or cFTP deployments and identify any r582 instances.
- Check ProjectSend vendor or project guidance for fixed versions or advisories.
- Restrict log export access to authorized administrative users only.
- Disable or isolate legacy r582 instances if no supported fix is available.
- Review logs for unexpected access to includes/actions.log.export.php.
Validation and detection
- Confirm whether includes/actions.log.export.php exists on deployed instances.
- Verify the running ProjectSend/cFTP version against r582.
- Review application authorization checks around log export functionality.
- Check web access logs for unusual log export requests.
- Document whether logs contain sensitive operational or user data.
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.
CVE-2016-10734 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.