dbcve.org
ProjectsendApplication

CVE-2016-10732

CRITICAL · 9.8 CVSS v3.0 Published 2018-10-29
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 · unedited
ProjectSend (formerly cFTP) r582 allows authentication bypass via a direct request for users.php, home.php, edit-file.php?file_id=1, or process-zip-download.php, or add_user_form_* parameters to users-add.php.

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 confidence

ProjectSend r582 contains an authentication bypass vulnerability where multiple sensitive PHP pages (users.php, home.php, edit-file.php, process-zip-download.php) and certain add_user_form_* parameters in users-add.php can be accessed directly without any authentication check, allowing unauthorized users to access administrative functions and potentially add or modify users.

MitigationImplement proper session validation and authentication checks at the beginning of all sensitive PHP files, remove or properly validate the vulnerable add_user_form_* parameters, and ensure all administrative pages require authenticated sessions.

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
ProjectsendApplication
Affected:= 582

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed ProjectSend version
    Locate the version file in your ProjectSend installation (commonly version.php, changelog.txt, or similar), or check the dashboard/admin interface for the software version
    Affected if The installed version is exactly r582 or 582
  2. Verify vulnerable PHP files exist
    Check if these files exist in your installation: users.php, home.php, edit-file.php, process-zip-download.php, and users-add.php in the appropriate admin or includes directories
    Affected if These files exist and your version is 582
  3. Test unauthenticated access to sensitive endpoints
    Attempt to access the vulnerable pages directly via HTTP request without logging in (e.g., visit your-projectsend-url/users.php, your-projectsend-url/home.php, etc.)
    Affected if The pages load without requiring authentication or a login session
  4. Check users-add.php for vulnerable parameters
    Inspect the users-add.php file source code for add_user_form_* parameters that lack authentication checks before processing
    Affected if The add_user_form_* parameters can be processed without prior authentication validation

You are affected if ProjectSend version 582 is installed and the sensitive PHP pages are accessible without authentication or the add_user_form_* parameters lack auth checks.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper session validation and authentication checks at the beginning of all sensitive PHP files, remove or properly validate the vulnerable add_user_form_* parameters, and ensure all administrative pages require authenticated sessions.

Recommended fix Moderate confidence

Latest stable release of ProjectSend (any version after r582 that includes the security fix)

  1. 1. Identify the current installed version of ProjectSend by checking the application or version file
  2. 2. Download the latest stable version of ProjectSend from the official GitHub repository (github.com/projectsend) or the official website
  3. 3. Before upgrading, backup the existing database and files to prevent data loss
  4. 4. Upload and install the latest version, following the standard upgrade documentation
  5. 5. Verify that the authentication bypass vulnerability is resolved by attempting to access the previously vulnerable URLs (users.php, home.php, edit-file.php, process-zip-download.php, users-add.php) without authentication - they should now require valid authentication
  6. 6. Test that normal authentication and authorization flows work correctly after the upgrade
Caveat Review release notes for any breaking changes between r582 and the target version, particularly regarding database schema changes or deprecated features

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Projectsend Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,580
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,328.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-10732 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-10732 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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