GHSA-4mmr-2w8p-whcr is a medium-severity (CVSS 5.3) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-4mmr-2w8p-whcr is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.
Mattermost improperly allows team administrators to modify team invites
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.1 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.6.0-rc1&&< 10.6.3 | 10.6.3 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 10.5.0-rc1&&< 10.5.4 | 10.5.4 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | ≥ 9.0.0-rc1&&< 9.11.13 | 9.11.13 |
| 🐹Go | github.com/mattermost/mattermost/server/v8 | all versions | 8.0.0-20250412152950-02c76784380a |
Detection & 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. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
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 GHSA-4mmr-2w8p-whcr is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-4mmr-2w8p-whcr is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.
Tailored to GHSA-4mmr-2w8p-whcr. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.
Frequently Asked Questions
Is GHSA-4mmr-2w8p-whcr in your dependencies?
O3 detects GHSA-4mmr-2w8p-whcr across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.