Skip to content
Fencer Vulns
high 7.1

CVE-2023-6458 json

Client side path traversal due to lack of route parameters validation

published 2023-12-06 2 y ago modified 2026-09-10 1 mo ago also BIT-mattermost-2023-6458 , EUVD-2023-3139 , GHSA-7664-hcp7-f497

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

Summary

Mattermost webapp fails to validate route parameters in/<TEAM_NAME>/channels/<CHANNEL_NAME> allowing an attacker to perform a client-side path traversal.

Patch / fix

  • go github.com/mattermost/mattermost-server/v6 7.8.14
  • go github.com/mattermost/mattermost/server/v8 8.1.5, 9.0.3
  • go github.com/mattermost/mattermost/server 9.1.2
  • bitnami mattermost 7.8.14, 8.1.5, 9.0.3, 9.1.2
  • Mattermost Mattermost 7.8.14, 8.1.5, 9.0.3, 9.1.2

Exploit prediction

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

CVSS scores

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

Affected packages

ecosystem package affected fixed in
go github.com/mattermost/mattermost-server/v6
<7.8.14
7.8.14
go github.com/mattermost/mattermost/server/v8
<8.1.5
>=9.0.0, <9.0.3
8.1.5
9.0.3
go github.com/mattermost/mattermost/server
>=9.1.0, <9.1.2
9.1.2
bitnami mattermost
<7.8.14
>=8.0.0, <8.1.5
>=9.0.0, <9.0.3
>=9.1.0, <9.1.2
7.8.14
8.1.5
9.0.3
9.1.2

Affected products

  • Mattermost Mattermost

Classification

Weakness
  • CWE-74 Improper Neutralization of Special Elements in Output Used by a Downstream Component
  • CWE-22 Improper Limitation of a Pathname to a Restricted Directory

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.