IntercomWordPress extension
CVE-2019-14365
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 · uneditedThe Intercom plugin through 1.2.1 for WordPress leaks a Slack Access Token in source code. An attacker can obtain a lot of information about the victim's Slack (channels, members, etc.).
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 confidenceThe Intercom WordPress plugin through version 1.2.1 exposes a Slack Access Token in its source code. An unauthenticated attacker can retrieve this token from the plugin's frontend JavaScript or API responses and use it to make authenticated Slack API calls, accessing channel listings, member information, and other workspace data.
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
IntercomWordPress extension
<= 1.2.1CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/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 if Intercom plugin is installedNavigate to WordPress admin > Plugins and look for 'Intercom' plugin, or inspect the wp-content/plugins directory for an intercom folder. Note the installed version number.Affected if Intercom plugin is installed with version 1.2.1 or lower
-
Verify the plugin version is vulnerableCompare the installed version against the affected range. In WordPress admin, the version is displayed on the Plugins page. If the version cannot be determined, assume it may be the bundled version <= 1.2.1.Affected if Installed version is 1.2.1 or any version up to 1.2.1, or version cannot be determined but plugin is present
-
Inspect frontend JavaScript for exposed Slack tokenVisit the website frontend and view page source or use browser developer tools to examine loaded JavaScript files. Search for strings matching Slack token patterns (typically starting with 'xoxb-' or 'xoxp-') or look for references to 'slack', 'access_token', or 'token' within the Intercom plugin's JS files.Affected if A Slack token string (xoxb- or xoxp- prefix) is found in any JavaScript file originating from the Intercom plugin
-
Check API responses for credential exposureUse browser developer tools to monitor network requests. Trigger Intercom plugin functionality (such as chat widgets or API endpoints at /wp-json/ or similar paths). Examine JSON responses for any exposed Slack access tokens.Affected if API responses from the plugin contain a Slack access token value
Your environment is affected if the Intercom WordPress plugin version 1.2.1 or lower is installed and active, with a Slack token visible in frontend JavaScript or API responses.
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 dataUpdate the Intercom plugin to the latest version if available, otherwise remove the plugin entirely. Additionally, immediately revoke the exposed Slack Access Token in the Slack workspace settings and generate a new token with restricted permissions.
Fix this in Intercom
Scoped from the published advisory
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-14365 — 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-14365 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