CVE-2021-26266
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 92.0.9 allows a Reseller to bypass the suspension lock (SEC-578).
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 92.0.9 contains an authorization bypass vulnerability where a Reseller-level user can bypass the suspension lock mechanism (SEC-578), potentially allowing access to or manipulation of suspended accounts that should be restricted.
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< 92.0.9CVSS 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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/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.
-
Identify cPanel versionAccess WHM and navigate to Server Status > cPanel Version, or run 'cat /usr/local/cpanel/version' via command line as rootAffected if The displayed version number is below 92.0.9
-
Confirm reseller-level accounts existLog into WHM as administrator and navigate to Reseller Center > View Resellers, or run 'whmapi1 listresellers' via command lineAffected if Any reseller accounts are present in the system
-
Check suspension lock status for resellersIn WHM, go to Reseller Center > Manage Reseller Suspension Locks, or inspect the reseller configuration via 'whmapi1 resellerstats' for each resellerAffected if Suspension lock is enabled for any reseller account, and that reseller can still access or manipulate suspended accounts
-
Test suspension lock bypassAs a reseller user, attempt to access or perform operations on an account that has been suspended by the administrator with the suspension lock feature activeAffected if The reseller can access or manipulate a suspended account despite the suspension lock being enabled
You are affected if cPanel version is below 92.0.9 and reseller accounts with suspension lock enabled exist in the environment, allowing those resellers unauthorized access to suspended accounts.
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 data92.0.9
Upgrade cPanel to version 92.0.9 or later to obtain the vendor patch, then verify the suspension lock functionality works correctly for reseller-managed 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-2021-26266 — 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-2021-26266 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