Skip to content
Fencer Intel
medium 4.3

CVE-2017-18878 json

Mattermost Server allows users with a session ID to revoke another users' session

published 2020-06-19 6 y ago modified 2026-06-17 4 mo ago also GHSA-h564-6gc2-fcc6 , GO-2025-4191 , EUVD-2017-9968

cvss
4.3
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. Knowledge of a session ID allows revoking another user's session.

Patch / fix

  • go github.com/mattermost/mattermost-server 4.1.2-0.20171004201910-6be8113eb60c, 4.2.1-0.20171004192657-8fbbd688ea24, 4.3.0, 4.3.0+incompatible
  • mattermost mattermost_server 4.1.2, 4.2.1
  • govulncheck-vulndb openSUSE Leap 15.6 0.0.20251230T014957-150000.1.134.1

suse advisories SUSE-SU-2026:0037-1

  • govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

Exploit prediction

0.78% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

assigned by version score vector
NVD 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L
NVD 2.0 4.0 AV:N/AC:L/Au:S/C:N/I:N/A:P
GitHub 3.1 4.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:N/A:L

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server
<4.1.2-0.20171004201910-6be8113eb60c
>=4.2.0-rc1, <4.2.1-0.20171004192657-8fbbd688ea24
>=4.3.0-rc1, <4.3.0
>=4.3.0-rc1+incompatible, <4.3.0+incompatible
4.1.2-0.20171004201910-6be8113eb60c
4.2.1-0.20171004192657-8fbbd688ea24
4.3.0
4.3.0+incompatible

Classification

Weakness
  • CWE-732 Incorrect Permission Assignment for Critical Resource
  • CWE-284 Improper Access Control
  • CWE-639 Authorization Bypass Through User-Controlled Key

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.