dbcve.org
Wp SlacksyncWordPress extension · Slack

CVE-2019-14366

HIGH · 7.5 CVSS v3.1 Published 2019-11-12
Fix available
A fix is available. Upgrade to after 1.8.5 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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 · unedited
WP SlackSync plugin through 1.8.5 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 confidence

The WP SlackSync WordPress plugin through version 1.8.5 exposes a Slack Access Token in its source code. Attackers who discover this token can authenticate to the associated Slack workspace API and enumerate channels, members, and other sensitive workspace data.

MitigationImmediately rotate the exposed Slack Access Token in the Slack workspace settings, update the plugin to the latest version if a patch is available, and audit Slack API access logs for unauthorized enumeration activity.

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
Wp SlacksyncWordPress extension
Affected:<= 1.8.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if WP SlackSync plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins and look for 'SlackSync' or 'WP SlackSync' in the plugin list
    Affected if Plugin is not present in the plugins list
  2. Verify the installed plugin version
    Click on the plugin name in the Plugins page to view details, or inspect the plugin header in the main plugin file (typically wp-content/plugins/slack-sync/ or similar naming) for the Version field
    Affected if Version number displayed is 1.8.5 or lower
  3. Confirm the plugin is active
    In the Plugins list, check if SlackSync shows as 'Active' under the status column
    Affected if Plugin status shows as Active
  4. Inspect plugin source code for exposed Slack token
    Access the plugin files via File Manager or FTP, locate the main plugin PHP file(s), and search for strings containing 'xoxb-' (Slack bot token format) or 'xoxp-' (Slack user token format) in the code
    Affected if Any Slack API token string (starting with xoxb- or xoxp-) is found hardcoded in the plugin source files

User is affected if WP SlackSync plugin version 1.8.5 or lower is installed, active, and contains a hardcoded Slack Access Token in its source code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 1.8.5
Interim mitigation

Immediately rotate the exposed Slack Access Token in the Slack workspace settings, update the plugin to the latest version if a patch is available, and audit Slack API access logs for unauthorized enumeration activity.

Fix this in Wp Slacksync Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-14366 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2019-14366 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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