Skip to content
Fencer Intel
high 7.3

CVE-2023-1776 json

Stored XSS via SVG attachment on Boards

published 3y ago modified 4mo ago also BIT-mattermost-2023-1776 , EUVD-2023-0891 , GHSA-63f2-6959-2pxj

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

Summary

Boards in Mattermost allows an attacker to upload a malicious SVG image file as an attachment to a card and share it using a direct link to the file.

Patch / fix

  • go github.com/mattermost/mattermost-server/v6 7.1.6
  • go github.com/mattermost/mattermost-server 7.1.6, 7.7.2, 7.8.1
  • go github.com/mattermost/mattermost-server/v5 7.1.6
  • bitnami mattermost 7.1.6
  • Mattermost Mattermost 7.1.6, 7.7.2, 7.8.0

Is CVE-2023-1776 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

CISA SSVC

Exploitation
none
Automatable
no
Technical impact
total
Assessed
last yr.

Exploit prediction

0.45% chance of exploitation in the next 30 days, higher than 39% of all scored CVEs (FIRST EPSS, 2026-11-15).

CVSS scores

assigned by version score vector
CNA 3.1 7.3 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:H/I:H/A:N
GitHub 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
NVD 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
OSV 3.1 5.4 CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server/v6
>=6.0.0, <7.1.6
>=3.3.0, <7.1.6
7.1.6
go github.com/mattermost/mattermost-server
>=7.7.0, <7.7.2
>=7.1.0, <7.1.6
>=7.8.0, <7.8.1
7.7.2
7.1.6
7.8.1
go github.com/mattermost/mattermost-server/v5
>=5.0.0, <7.1.6
7.1.6
bitnami mattermost
<7.1.6
>=7.7.1, <=7.7.1
7.1.6

Affected products

  • Mattermost Mattermost

Classification

Weakness
  • CWE-79 Improper Neutralization of Input During Web Page Generation

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.