6.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Concerned about an active attack path?

Talk to our security experts and see Miggo in action.

Miggo Vulnerability Database

→

CVE-2025-6233

CVE-2025-6233: Mattermost Path Traversal vulnerability

Mattermost versions 10.8.x <= 10.8.1, 10.7.x <= 10.7.3, 10.5.x <= 10.5.7, 9.11.x <= 9.11.16 fail to sanitize input paths of file attachments in the bulk import JSONL file, which allows a system admin to read arbitrary system files via path traversal.

(GitHub Advisory)

Miggo Vulnerability Database

→

CVE-2025-6233

CVE-2025-6233:

6.8

CVSS Score

3.1

-

CVSS Score

Basic Information

Is this CVE running in your environment?

Easily map the attack path and prioritize which CVEs are a threat to your organization

Validate Exposure

Technical Details

Package Name	Ecosystem	Vulnerable Versions	First Patched Version
github.com/mattermost/mattermost-server	go	>= 10.8.0, < 10.8.2	10.8.2
github.com/mattermost/mattermost-server	go	>= 10.7.0, < 10.7.4	10.7.4
github.com/mattermost/mattermost-server	go	>= 10.5.0, < 10.5.8	10.5.8
github.com/mattermost/mattermost-server	go	>= 9.11.0, < 9.11.17	9.11.17
github.com/mattermost/mattermost/server/v8	go	< 8.0.0-20250529054450-d38c27f96fcf	8.0.0-20250529054450-d38c27f96fcf

Technical Details

Vulnerability Intelligence
Miggo AI

Root Cause Analysis

The vulnerability is a classic path traversal issue within the bulk import functionality of Mattermost. The root cause was the failure to sanitize and validate user-provided file paths for various types of attachments (posts, replies, user/bot profile images, and custom emojis) contained within the imported JSONL file.

The investigation of the patch d38c27f96fcf754c36f231d1f2e9dbd48ad40bab reveals that several functions were involved. The functions processAttachmentPaths and processAttachments in server/channels/app/import.go were directly responsible for constructing file paths using the unsafe filepath.Join function on raw input. This is where the traversal was physically constructed.

Furthermore, a set of validation functions within server/channels/app/imports/import_validators.go (e.g., ValidatePostImportData, ValidateUserImportData) were also culpable. These functions were supposed to validate the integrity of the import data but were missing the crucial checks for attachment paths. An attacker with system admin privileges could craft a malicious import file with ../ sequences in the path fields of attachment objects, causing the server to read and potentially expose arbitrary files from the filesystem during the import process.

The patch rectifies this by introducing a new, centralized validation function, ValidateAttachmentPathForImport, which ensures that any resolved path is strictly within the intended base directory. This new function is then called from all the previously vulnerable validation and processing functions, effectively closing the security hole through a defense-in-depth approach.

Vulnerable functions

Only Mi**o us*rs **n s** t*is s**tion

Vulnerability Intelligence
Miggo AI

Unlock WAF rules for this CVE

Generate vendor-ready rules for the observed attack patterns, plus reasoning and safe deployment guidance

Get WAF rules

WAF Protection Rules

WAF Rule

W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.W** rul*s *v*il**l* *or Mi**o *ustom*rs only.

Reasoning

*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.*v*il**l* *or Mi**o *ustom*rs only.