CVE-2020-10117
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 84.0.20 mishandles enforcement of demo checks in the Market UAPI namespace (SEC-542).
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 84.0.20 fails to properly enforce demo mode restrictions in the Market UAPI namespace, allowing authenticated users to bypass demo check controls and execute operations that should be restricted in demo mode. This could enable unauthorized administrative or billing operations through the Market API.
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>= 77.9999.110, < 78.0.45>= 83.9999.115, < 84.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/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 versionRun 'cat /usr/local/cpanel/version' or 'cpanel -V' to obtain the installed cPanel version numberAffected if The version falls within >=77.9999.110 and <78.0.45, OR >=83.9999.115 and <84.0.20
-
Confirm demo mode is activeCheck for the existence of /var/cpanel/demo mode file or inspect the cPanel demo configuration at /var/cpanel/users/username for demo=1 settingAffected if Demo mode is enabled on the account being tested, because the vulnerability only allows bypassing demo restrictions
-
Verify Market UAPI namespace is accessibleAttempt to access a Market UAPI function via command line: /usr/local/cpanel/bin/uapi --module=Market --function=get_providers, or check if the Market module is loaded in /usr/local/cpanel/UAPI/Modules/Affected if The Market UAPI module is installed and accessible to the authenticated user context being tested
A system is affected only if it runs a cPanel version within the specified ranges AND has demo mode enabled, allowing the Market UAPI namespace to be accessed when it should be restricted.
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.
dbcve · scoped78.0.4584.0.20
Upgrade cPanel to version 84.0.20 or later to remediate the demo check enforcement bypass in the Market UAPI namespace.
cPanel version 84.0.20 (or 78.0.45 for the 78 branch)
- Log into WHM (Web Host Manager) as the root user
- Navigate to: Home >> cPanel >> Upgrade to Latest Version
- Click 'Upgrade to Latest Version' button to initiate the cPanel upgrade
- Alternatively, run '/scripts/upcp' via command line as root to perform the upgrade
- After upgrade completes, verify the version is 84.0.20 or later (or 78.0.45 or later for the 78 branch) using: 'cat /usr/local/cpanel/version'
- Verify the fix by confirming demo mode restrictions are properly enforced in the Market UAPI namespace
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10117 — 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-10117 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