CVE-2019-17377
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 82.0.15 allows self XSS in LiveAPI example scripts (SEC-524).
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 confidenceSelf XSS vulnerability in cPanel's LiveAPI example scripts versions prior to 82.0.15. Self XSS requires the victim to unknowingly paste malicious JavaScript into their browser (typically via the address bar or developer console), making it less exploitable than standard stored or reflected XSS. The vulnerability exists in example scripts that ship with cPanel's LiveAPI functionality.
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.39>= 81.9999.242, < 82.0.15CVSS 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.
-
Check cPanel versionRun 'whmapi1 version' via command line or access WHM > Server Information to view the installed cPanel versionAffected if Version is between 77.9999.110 and 78.0.39, or between 81.9999.242 and 82.0.15 (excluding 82.0.15)
-
Verify LiveAPI module is presentCheck for the presence of LiveAPI-related directories in /usr/local/cpanel/base/frontend/ or locate example scripts with 'find /usr/local/cpanel -name "*liveapi*" -type f'Affected if LiveAPI example scripts exist in the cPanel frontend directory
-
Check LiveAPI documentation endpoint accessibilityAttempt to access the LiveAPI documentation endpoint (typically at /cpanelwebcall/ or /liveapi/ paths) or inspect cPanel.conf for LiveAPI-related configurationAffected if LiveAPI documentation or example endpoints are accessible without authentication restrictions
-
Inspect example scripts for unsanitized inputExamine the source code of LiveAPI example scripts (such as index.cgi, liveapi.js, or similar) for lack of input sanitization on user-controlled parametersAffected if Example scripts contain JavaScript code that reflects user input without proper escaping
Your environment is affected if running a cPanel version in the ranges 77.9999.110-78.0.39 or 81.9999.242-82.0.15 AND the LiveAPI example scripts are present and accessible on your server.
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.3982.0.15
Upgrade cPanel to version 82.0.15 or later to obtain the patched LiveAPI example scripts. As a defensive measure, restrict access to LiveAPI documentation and example endpoints to trusted administrators only until patching is complete.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17377 — 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-2019-17377 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