Skip to content
Fencer Vulns
medium 4.3

CVE-2024-1887 json

Public channel post content accessible without membership when compliance export is enabled

published 2024-02-29 2 y ago modified 2026-09-10 1 mo ago also GHSA-fx48-xv6q-6gp3 , GO-2024-2591 , EUVD-2024-0634

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

Summary

Mattermost fails to check if compliance export is enabled when fetching posts of public channels allowing a user that is not a member of the public channel to fetch the posts, which will not be audited in the compliance export.

Patch / fix

  • go github.com/mattermost/mattermost/server/v8 8.1.9, 9.2.5, 9.3.1
  • go github.com/mattermost/mattermost-server 9.2.5+incompatible, 9.3.1+incompatible
  • Mattermost Mattermost 8.1.9, 9.2.5, 9.3.1, 9.4.0

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
partial
Assessed
2 y ago

Exploit prediction

0.33% chance of exploitation in the next 30 days, higher than 26% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost/server/v8
>=9.3.0, <9.3.1
>=9.2.0, <9.2.5
<8.1.9
all versions
9.3.1
9.2.5
8.1.9
go github.com/mattermost/mattermost-server
>=9.2.0+incompatible, <9.2.5+incompatible
>=9.3.0+incompatible, <9.3.1+incompatible
9.2.5+incompatible
9.3.1+incompatible
go github.com/mattermost/mattermost-server/v5
all versions
no fix listed
go github.com/mattermost/mattermost-server/v6
all versions
no fix listed

Affected products

  • Mattermost Mattermost

Classification

Weakness

References

Sources

Fencer Vulns 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.