WordPress security changelog
HIGH CVE-2019-14366 Modified

Wp Slacksync: A security weakness

Wp Slacksync is affected by a security weakness. Exposure depends on how the affected operation is made reachable by the site. The resulting impact depends on how the affected component exposes the vulnerable operation.

CVE / CNA score 7.5 CVSS · cve@mitre.org
NVD score 7.5 CVSS 3.1 · nvd@nist.gov
Component
Wp Slacksync
Plugin slug
wp-slacksync
Affected
See vendor advisory
Safe version
See mitigation notes
Published
Nov 12, 2019
Weakness
CWE-200 — Exposure of Sensitive Information to an Unauthorized Actor

This CVE was published Nov 12, 2019 and is one of 1 known issue for this plugin.

Update, patch or deactivate.

Update Wp Slacksync to a release outside the affected range, or disable and remove it until a fixed version is available.

No confirmed safe version is listed. Consider a vendor-supported patch or temporarily restricting the affected functionality while you assess the risk.

Deactivate only when warranted by your risk profile, or when advised by your hosting provider in the limited circumstances where the vulnerability cannot otherwise be mitigated. If you’re unsure which action is appropriate, contact Fused or your hosting provider for guidance.

Technical description

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.).

NVD vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Primary and upstream sources