CVE-2016-10731
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 · uneditedProjectSend (formerly cFTP) r582 allows SQL injection via manage-files.php with the request parameter status, manage-files.php with the request parameter files, clients.php with the request parameter selected_clients, clients.php with the request parameter status, process-zip-download.php with the request parameter file, or home-log.php with the request parameter action.
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 confidenceCritical SQL injection vulnerability in ProjectSend r582 where multiple PHP files (manage-files.php, clients.php, process-zip-download.php, home-log.php) accept unsanitized user input via request parameters (status, files, selected_clients, file, action) directly in SQL queries, allowing attackers to manipulate database operations.
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= 582CVSS 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
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Verify ProjectSend installation existsCheck for the presence of ProjectSend files in the web root directory. Look for the typical installation path such as /var/www/html/ or C:\inetpub\wwwroot\ and locate ProjectSend-specific directories and PHP files.Affected if ProjectSend is installed on the server
-
Identify the installed ProjectSend versionLocate the version file or header within the ProjectSend installation. Check files like version.txt, info.php, or the main index.php for a version number. The vulnerable version is exactly r582.Affected if The installed version is precisely r582 (not higher or patched)
-
Confirm vulnerable PHP files are presentVerify that manage-files.php, clients.php, process-zip-download.php, and home-log.php exist in the ProjectSend installation directory, typically within the root or includes folder.Affected if Any of these four PHP files exist in the installation
-
Check if the application is accessible and processing requestsDetermine if the web application is actively running by attempting to access the login page or checking if the database connection is active. The vulnerability requires the application to be running and accepting requests.Affected if The web application is accessible and processing PHP requests
You are affected if ProjectSend r582 is installed and the vulnerable PHP files are accessible, as the SQL injection exists in the direct use of user input in SQL queries for the status, files, selected_clients, file, and action parameters.
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.
From vendor dataUpgrade to a patched version of ProjectSend that addresses these SQL injection vulnerabilities, or implement parameterized queries/prepared statements for all database interactions in the affected files to prevent injection.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10731 — 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-2016-10731 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