Skip to content
Fencer Intel
medium 5.3

CVE-2020-14457 json

Mattermost Server Sensitive Data Exposure

published 6y ago modified 4mo ago also BIT-mattermost-2020-14457 , EUVD-2022-4257 , GHSA-j2h2-cvwh-cr64 , GO-2023-1939

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

Summary

An issue was discovered in Mattermost Server before 5.20.0. Non-members can receive broadcasted team details via the update_team WebSocket event, aka MMSA-2020-0012.

Patch / fix

  • go github.com/mattermost/mattermost-server/v5 5.20.0
  • bitnami mattermost 5.20.0
  • mattermost mattermost_server 5.20.0

Is CVE-2020-14457 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.92% chance of exploitation in the next 30 days, higher than 60% of all scored CVEs (FIRST EPSS, 2026-11-09).

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server/v5
<5.20.0
5.20.0
bitnami mattermost
<5.20.0
5.20.0
go github.com/mattermost/mattermost
all versions
no fix listed
go github.com/mattermost/mattermost-server
all versions
no fix listed

Classification

Weakness

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.