CVE-2018-20874
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 74.0.8 allows self XSS in the WHM "Create a New Account" interface (SEC-428).
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 · high confidencecPanel before version 74.0.8 contains a self Cross-Site Scripting (XSS) vulnerability in the WHM (Web Host Manager) 'Create a New Account' interface. A self XSS vulnerability means the malicious script only executes when the attacker visits their own injected payload, limiting exploitation scope compared to stored or reflected XSS.
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>= 69.9999.122, < 70.0.57>= 73.9980.0, < 74.0.8CVSS 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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/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 versionLog into WHM and navigate to 'Server Information' or run command: cat /usr/local/cpanel/versionAffected if The version falls within >= 69.9999.122 and < 70.0.57, OR >= 73.9980.0 and < 74.0.8
-
Confirm WHM accessAccess Web Host Manager at https://yourserver:2087 or https://yourserver:2086 and verify login credentialsAffected if WHM is accessible and you can reach the 'Create a New Account' interface
-
Locate Create a New Account interfaceIn WHM, navigate to Account Functions > Create a New Account or search for 'Create a New Account' in the search barAffected if The interface exists and is accessible in the WHM interface
You are affected if your cPanel version is between 69.9999.122 and 70.0.57 (exclusive of 70.0.57) OR between 73.9980.0 and 74.0.8 (exclusive of 74.0.8), AND you have access to the WHM Create a New Account feature.
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 data70.0.5774.0.8
Upgrade cPanel to version 74.0.8 or later to patch the self XSS vulnerability in the WHM Create a New Account interface.
- Consultation1.0 h
- Implementation1.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,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2018-20874 — 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-20874 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