CVE-2018-20928
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 stored XSS via the cpaddons vendor interface (SEC-391).
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 confidenceA stored Cross-Site Scripting (XSS) vulnerability exists in cPanel versions before 70.0.23. The vulnerability is located in the cpaddons vendor interface, allowing an attacker to inject malicious JavaScript that persists on the server and executes when other users access the affected interface.
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
- None
- User interaction
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.0/AV:N/AC:L/PR:N/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 versionRun the command: /usr/local/cpanel/cpanel -V or cat /usr/local/cpanel/version.txtAffected if The displayed version falls within these ranges: >= 61.9999.55 and < 62.0.42; OR >= 67.9999.64 and < 68.0.33; OR >= 69.9999.122 and < 70.0.23
-
Confirm cpaddons vendor interface presenceCheck if the cpaddons feature is accessible by logging into cPanel as an administrator and navigating to the vendor interface section, or by checking for the cpaddons configuration at /var/cpanel/addons/Affected if The cpaddons vendor interface exists and is accessible in the cPanel installation
-
Verify version against all affected branchesCompare your installed version number against each of the three affected version ranges listed in the CVEAffected if Your version matches any of the three vulnerable ranges (61.x between 61.9999.55-61.9999.999, 67.x between 67.9999.64-67.9999.999, or 69.x between 69.9999.122-69.9999.999)
You are affected if your cPanel installation runs version 62.0.42 or higher but below that branch's safe threshold, or versions 67.x below 68.0.33, or 69.x below 70.0.23, and the cpaddons vendor interface is accessible.
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
Update cPanel to version 70.0.23 or later to apply the vendor patch that addresses this stored XSS vulnerability in the cpaddons vendor interface.
- 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-2018-20928 — 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-20928 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