CVE-2019-17375
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 API token credentials to persist after an account has been renamed or terminated (SEC-517).
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.15 fails to revoke API token credentials when an account is renamed or terminated. This allows stale API tokens to remain valid even after the associated account no longer exists or has been renamed, potentially enabling unauthorized access using abandoned credentials.
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>= 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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 your cPanel versionRun the command to retrieve the cPanel version (typically found in /usr/local/cpanel/version or via WHM API). Compare the installed version against the affected range: 81.9999.242 through 82.0.14.Affected if The installed version falls within >= 81.9999.242 and < 82.0.15
-
Identify renamed accountsReview your account renaming logs or audit records to list any accounts that were renamed after the cPanel installation reached version 81.9999.242 or later.Affected if Any accounts were renamed in the affected version range and their old API tokens were not explicitly revoked
-
Identify terminated accountsReview your account termination logs or audit records to list any accounts that were terminated after the cPanel installation reached version 81.9999.242 or later.Affected if Any accounts were terminated in the affected version range and their API tokens were not explicitly revoked
-
Audit API tokens for renamed accountsFor each renamed account identified, use the cPanel API token management interface or command-line tools to list all API tokens and check whether tokens created under the old account name remain valid.Affected if API tokens from the old account name are still functional after the account was renamed
-
Audit API tokens for terminated accountsFor each terminated account identified, attempt to authenticate using previously issued API tokens for that account. Check whether those tokens are still accepted by the API.Affected if API tokens from terminated accounts are still accepted and functional
You are affected if your cPanel version is between 81.9999.242 and 82.0.14 AND you have renamed or terminated any accounts in that version range without manually revoking their API tokens.
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.15
Upgrade cPanel to version 82.0.15 or later to receive the patch. Additionally, review and rotate API tokens for any accounts that were renamed or terminated prior to the upgrade.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-17375 — 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-17375 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