CVE-2018-20931
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 70.0.23 allows demo accounts to execute code via the Landing Page (SEC-405).
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 70.0.23 contains a code execution vulnerability in the Landing Page component. Demo accounts, which are typically restricted demonstration accounts, can bypass restrictions and execute arbitrary code through the Landing Page feature.
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>= 61.9999.55, < 62.0.42>= 67.9999.64, < 68.0.33>= 69.9999.122, < 70.0.23CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
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 installationRun 'cat /usr/local/cpanel/version' or check '/usr/local/cpanel/version' file to get the installed cPanel versionAffected if The system does not have cPanel installed - this CVE does not apply
-
Compare version against affected rangesCompare the installed version to these affected ranges: 61.9999.55 to 62.0.42, 67.9999.64 to 68.0.33, or 69.9999.122 to 70.0.23Affected if The version falls within any of these ranges (less than 62.0.42, 68.0.33, or 70.0.23)
-
Verify demo account existenceCheck for demo accounts in cPanel using WHM API or by examining /var/cpanel/users/ directory for accounts with demo flag, or run 'whmapi1 listaccounts' and look for accounts with demo=1Affected if Demo accounts exist in the cPanel environment
-
Check Landing Page feature statusInspect cPanel configuration for Landing Page module status, typically found in /var/cpanel/configs/cpanel.config or check via WHM API 'whmapi1 get_feature_list' for landing_page featureAffected if Landing Page feature is enabled in cPanel features list
The environment is affected if cPanel is installed with a version in the affected ranges AND demo accounts exist AND the Landing Page feature is enabled, allowing demo users to potentially execute arbitrary code.
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 data62.0.4268.0.3370.0.23
Upgrade cPanel to version 70.0.23 or later to patch this code execution vulnerability in demo accounts.
- Consultation2.0 h
- Implementation3.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 $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20931 — 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-2018-20931 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