CVE-2025-3913 is a medium-severity (CVSS 5.3) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. A fix is available for github.com/mattermost/mattermost/server/v8 — see the affected versions and patch details below.
Team Privacy Settings Authorization Bypass in Mattermost Server
Exploitation Status
No confirmed exploitation observed yet
- CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for CVE-2025-3913.
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8🐹github.com/mattermost/mattermost/server/v8Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
Mattermost versions 10.7.x <= 10.7.0, 10.6.x <= 10.6.2, 10.5.x <= 10.5.3, 9.11.x <= 9.11.12 fail to properly validate permissions when changing team privacy settings, allowing team administrators without the 'invite user' permission to access and modify team invite IDs via the /api/v4/teams/:teamId/privacy endpoint.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.7.0-rc1&&< 10.7.1 | 10.7.1go get github.com/mattermost/mattermost/server/v8@v10.7.1 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.6.0-rc1&&< 10.6.3 | 10.6.3go get github.com/mattermost/mattermost/server/v8@v10.6.3 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.5.0-rc1&&< 10.5.4 | 10.5.4go get github.com/mattermost/mattermost/server/v8@v10.5.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.0.0-rc1&&< 9.11.13 | 9.11.13go get github.com/mattermost/mattermost/server/v8@v9.11.13 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20250412152950-02c76784380ago get github.com/mattermost/mattermost/server/v8@v8.0.0-20250412152950-02c76784380a |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost/server/v8, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost/server/v8 to 10.7.1 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-3913 is resolved across your whole dependency graph.
Workarounds
Put an independent control in front of the weakness: restrict the affected endpoint or interface to trusted networks, require an additional authentication factor or proxy-level check, and invalidate existing sessions and credentials in case the flaw has already been used.
Frequently Asked Questions
Is CVE-2025-3913 in your dependencies?
Find it across Go, including transitive dependencies.