CVE-2020-29136
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 · uneditedIn cPanel before 90.0.17, 2FA can be bypassed via a brute-force approach (SEC-575).
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 confidenceIn cPanel before version 90.0.17, the two-factor authentication (2FA) mechanism can be bypassed through a brute-force attack approach, allowing an attacker to potentially guess or iterate through valid 2FA codes to gain unauthorized access to accounts.
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.86.0.32>= 11.90.0, < 11.90.0.17>= 11.92.0, < 11.92.0.2CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:N/A:N
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 '/usr/local/cpanel/cpanel -V' or check /usr/local/cpanel/version file to obtain the installed cPanel versionAffected if The installed version is less than 11.86.0.32, OR between 11.90.0.0 and 11.90.0.16 inclusive, OR between 11.92.0.0 and 11.92.0.1 inclusive
-
Verify 2FA is enabledCheck if Two-Factor Authentication is configured for any user accounts by reviewing /var/cpanel/users/ directory or via WHM API call 'uapi --user=username TwoFactorAuthentication get_user_configuration'Affected if Two-Factor Authentication is enabled and the cPanel version falls within the affected ranges listed above
-
Check for brute-force protectionReview /etc/cpanel/cpanel.conf for 'BruteForce' related settings, or check if cPHulkd (cPanel's brute-force protection service) is enabled and running via '/scripts/cphulkd status'Affected if Brute-force protection is disabled or not properly configured on the 2FA authentication endpoints
Your environment is affected if you are running a cPanel version in the affected ranges AND have Two-Factor Authentication enabled, without adequate brute-force protection in place.
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.86.0.3211.90.0.1711.92.0.2
Upgrade cPanel to version 90.0.17 or later to remediate this vulnerability. Additionally, implement rate-limiting on 2FA endpoints and monitor for brute-force patterns as a defensive measure.
- 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-2020-29136 — 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-2020-29136 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