Mattermost Server has Improper Authorization for Integration Requests

published 2020-06-19 6y ago modified 2026-06-17 4mo ago also GHSA-x33g-375j-jhf7 , GO-2026-4467 , EUVD-2017-10006

cvss: 5.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

An issue was discovered in Mattermost Server before 3.8.2, 3.7.5, and 3.6.7. API endpoint access control does not honor an integration permission restriction.

Patch / fix

fixed in 2 distros 2 links 3

go github.com/mattermost/mattermost-server 3.6.7-0.20170420152529-0968e4079e0a, 3.7.5, 3.7.5+incompatible, 3.8.2, 3.8.2+incompatible
mattermost mattermost_server 3.6.7, 3.7.5, 3.8.2

suse opensuse

govulncheck-vulndb openSUSE Leap 15.6 0.0.20260226T182644-150000.1.149.1

suse advisories SUSE-SU-2026:0757-1

govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1

opensuse advisories openSUSE-SU-2026:21483-1

github.com/mattermost/mattermost@0968e40 commit
github.com/mattermost/mattermost@b74e856 commit
github.com/mattermost/mattermost@fb325cc commit

Is CVE-2017-18916 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

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	5.3	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N
NVD	2.0	5.0	AV:N/AC:L/Au:N/C:N/I:P/A:N

Affected packages

ecosystem	package	affected	fixed in
go	github.com/mattermost/mattermost-server	<3.6.7-0.20170420152529-0968e4079e0a >=3.7.0, <3.7.5 >=3.8.0, <3.8.2 >=3.7.0+incompatible, <3.7.5+incompatible >=3.8.0+incompatible, <3.8.2+incompatible	3.6.7-0.20170420152529-0968e4079e0a 3.7.5 3.8.2 3.7.5+incompatible 3.8.2+incompatible

Classification

Weakness

CWE-732 Incorrect Permission Assignment for Critical Resource
CWE-284 Improper Access Control

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.