CVE-2016-10826
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 attackers to bypass Two Factor Authentication via DNS clustering requests (SEC-93).
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 confidencecPanel before version 55.9999.141 contains a vulnerability that allows attackers to bypass Two Factor Authentication by sending specially crafted DNS clustering requests. This defeats the 2FA security control, allowing unauthorized access to affected cPanel installations.
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.52.0.5, < 11.52.4.1>= 11.54.0.0, < 11.54.0.20CVSS 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.
-
Identify cPanel installation and versionRun 'cat /usr/local/cpanel/version' or use WHM API: 'whmapi1 version' to retrieve the installed cPanel version numberAffected if The installed version falls within these ranges: 11.50.0.4 through 11.50.5.2, 11.52.0.5 through 11.52.4.1, or 11.54.0.0 through 11.54.0.20 (any version before 55.9999.141 is affected)
-
Verify DNS Clustering feature statusIn WHM, navigate to 'DNS Clustering' in the cluster section, or run: 'whmapi1 get_cluster_status' to check if DNS clustering is enabledAffected if DNS Clustering is enabled - this is the attack vector required to exploit the vulnerability
-
Confirm Two Factor Authentication is enabledIn cPanel/WHM, check 'Security' section for 'Two-Factor Authentication' status, or check via API: 'whmapi1 get_two_factor_auth_status'Affected if Two Factor Authentication is enabled - the vulnerability specifically bypasses this security control, so it is only relevant when 2FA is configured
Your environment is affected if cPanel version is before 55.9999.141 (within the affected ranges), DNS Clustering is enabled, and Two Factor Authentication has been configured.
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 to patch the Two Factor Authentication bypass vulnerability. After updating, verify that 2FA functions correctly.
- Consultation2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10826 — 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-10826 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