CVE-2016-10834
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 · uneditedcPanel before 55.9999.141 allows account-suspension bypass via ftp (SEC-105).
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 · moderate confidenceThis vulnerability in cPanel versions before 55.9999.141 allows authenticated users to bypass account suspension restrictions by using the FTP protocol. When an account is suspended in cPanel (typically for non-payment or policy violations), the suspension should block all access including FTP, but this flaw permits suspended accounts to maintain FTP connectivity.
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>= 11.50.0.4, < 11.50.5.2>= 11.51.9999.98, < 11.52.4.1>= 11.54.0.0, < 11.54.0.20>= 55.9999.61, < 55.9999.141CVSS 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:L/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.
-
Check cPanel versionRun command: /usr/local/cpanel/cpanel -V or access WHM and check the cPanel version information displayed in the footerAffected if The installed version falls within any of these ranges: 11.50.0.4 to 11.50.5.2, 11.51.9999.98 to 11.52.4.1, 11.54.0.0 to 11.54.0.20, or 55.9999.61 to 55.9999.141 (all versions before 55.9999.141 are affected)
-
Verify FTP server is runningRun command: service pure-ftpd status or systemctl status pure-ftpd or check in WHM under FTP Server statusAffected if FTP daemon (pure-ftpd or similar) is actively running on the server
-
Identify suspended accounts on the systemRun command in WHM: list_suspended or check /var/cpanel/suspended/ directory for suspended account filesAffected if There are accounts currently suspended in cPanel
-
Test FTP access with a suspended accountAttempt FTP connection using credentials of a suspended account: ftp localhost or ftp server_ip using the suspended account's username and passwordAffected if The FTP connection succeeds and authentication is granted for a suspended account (this confirms the vulnerability is present and exploitable)
You are affected if your cPanel version is before 55.9999.141 AND FTP is enabled AND at least one account is suspended AND suspended accounts can still connect via FTP.
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 data11.50.5.211.52.4.111.54.0.20
Upgrade cPanel to version 55.9999.141 or later. Alternatively, if immediate upgrade is not possible, consider temporarily disabling FTP access for all accounts or implementing additional firewall rules to block FTP traffic for suspended accounts.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10834 — 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-10834 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