CVE-2020-10114
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 allows stored self-XSS via the HTML file editor (SEC-535).
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 84.0.20 contains a stored cross-site scripting (XSS) vulnerability in the HTML file editor feature. The vulnerability allows injection of malicious script content that persists on the server and executes when users view the affected content.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/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.
-
Determine installed cPanel versionRun command: /usr/local/cpanel/cpanel -V or check /usr/local/cpanel/version fileAffected if Version is 77.9999.110 or higher but below 78.0.45, OR 83.9999.115 or higher but below 84.0.20
-
Verify HTML file editor feature is accessibleCheck if the File Editor feature exists in cPanel by examining /var/cpanel/features or consulting cPanel documentation for your versionAffected if The HTML file editor feature is enabled and accessible in the cPanel interface
-
Identify HTML files edited via File ManagerReview web server access logs for requests to /execute/FileManager/editit endpoint or check /var/cpanel/users/ directory for recently modified HTML files in user public_html directoriesAffected if HTML files exist that were edited using the cPanel File Manager editor
-
Inspect HTML files for suspicious script contentSearch modified HTML files for patterns like <script> tags, javascript: URLs, or event handlers (onclick, onload, etc.) that were not intentionally added by administratorsAffected if HTML files contain unexpected script tags or JavaScript event handlers that could indicate XSS injection
-
Review user account activity logsCheck /usr/local/cpanel/logs/access_log or /var/log/cpanel аудит logs for requests to the file editor containing unusual content patternsAffected if Editor access logs show injection attempts or unusual content being saved through the file editor interface
A system is affected if it runs a cPanel version between 77.9999.110-78.0.44 or 83.9999.115-84.0.19 AND the HTML file editor feature has been used to edit HTML files that may contain injected malicious scripts.
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 data78.0.4584.0.20
Upgrade cPanel to version 84.0.20 or later to obtain the security patch for this vulnerability.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.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 $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-10114 — 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-10114 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