CVE-2019-14390
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.2 has stored XSS in the WHM Modify Account interface (SEC-512).
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 82.0.2 contains a stored cross-site scripting (XSS) vulnerability in the WHM (Web Host Manager) Modify Account interface. An attacker with appropriate WHM access could inject malicious JavaScript code into account modification fields that would persist and execute in the browsers of other WHM users viewing the affected accounts.
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< 82.0.2CVSS 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.
-
Determine your cPanel versionLog into WHM and navigate to Server Status > cPanel Version, or run 'whmapi1 version' via command lineAffected if The installed version is earlier than 82.0.2
-
Verify WHM access is enabledConfirm that Web Host Manager (WHM) is accessible and active on your serverAffected if WHM is enabled and accessible to any user
-
Identify WHM user accounts with Modify Account privilegesReview user accounts in WHM > Resellers or WHM > List Accounts that have permission to modify hosting accountsAffected if More than one WHM user account exists with account modification privileges
-
Inspect recent account modifications for suspicious contentReview WHM account modification logs or audit logs for entries containing unusual characters or scripts in account fields (package, domain, contact email, etc.)Affected if Any account modification entries contain '<script>' tags, 'javascript:' URIs, or other XSS payloads in input fields
-
Examine stored account data for injected scriptsCheck the cPanel account database or use WHM API to query account details for any JavaScript or HTML in custom fields, notes, or contact informationAffected if Any stored account data contains executable JavaScript or suspicious HTML tags
You are affected if your cPanel version is earlier than 82.0.2 and you have multiple WHM users who can access the Modify Account interface.
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 data82.0.2
Upgrade cPanel to version 82.0.2 or later. Until patched, limit WHM access to trusted administrators and monitor for suspicious account modifications.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14390 — 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-14390 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