How severe is GHSA-6xjj-v76v-fwpj?

GHSA-6xjj-v76v-fwpj has a CVSS score of 6.7/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-6xjj-v76v-fwpj?

GHSA-6xjj-v76v-fwpj affects the following packages: github.com/mattermost/mattermost-server/v6 (Go), github.com/mattermost/mattermost-server/v6 (Go), github.com/mattermost/mattermost-server/v6 (Go). Ecosystems affected: Go.

How do I fix GHSA-6xjj-v76v-fwpj?

Update github.com/mattermost/mattermost-server/v6 to 7.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xjj-v76v-fwpj is resolved across your whole dependency graph.

How do I detect GHSA-6xjj-v76v-fwpj in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server/v6. 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.

How do I mitigate GHSA-6xjj-v76v-fwpj if there is no patch (or I can't update yet)?

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 does O3 Security protect against GHSA-6xjj-v76v-fwpj?

O3 pinpoints whether GHSA-6xjj-v76v-fwpj is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-6xjj-v76v-fwpj actively exploited in the wild?

No public exploit code has been indexed for GHSA-6xjj-v76v-fwpj yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What type of vulnerability is GHSA-6xjj-v76v-fwpj?

GHSA-6xjj-v76v-fwpj is classified as CWE-863 (CWE-863). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-6xjj-v76v-fwpj published, and has it been updated?

GHSA-6xjj-v76v-fwpj was published on August 11, 2023 and was last updated on November 8, 2023. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-6xjj-v76v-fwpj

MEDIUM

GHSA-6xjj-v76v-fwpj is a medium-severity (CVSS 6.7) CWE-863 vulnerability in github.com/mattermost/mattermost-server/v6. O3 Security confirms whether GHSA-6xjj-v76v-fwpj is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost does not validate requesting user permissions before updating admin details

Also known asCVE-2023-4107

Published

Aug 11, 2023

Updated

Nov 8, 2023

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Real-World Exposure

3 pkgs affected

🐹github.com/mattermost/mattermost-server/v6🐹github.com/mattermost/mattermost-server/v6🐹github.com/mattermost/mattermost-server/v6

Real-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 fails to properly validate the requesting user permissions when updating a system admin, allowing a user manager to update a system admin's details such as email, first name and last name.

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server/v6`	all versions	7.8.8
🐹Go	`github.com/mattermost/mattermost-server/v6`	≥ 7.9.0&&< 7.9.6	7.9.6
🐹Go	`github.com/mattermost/mattermost-server/v6`	≥ 7.10.0&&< 7.10.4	7.10.4

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server/v6. 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/v6 to 7.8.8 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-6xjj-v76v-fwpj 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-6xjj-v76v-fwpj 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-6xjj-v76v-fwpj. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

Mattermost fails to properly validate the requesting user permissions when updating a system admin, allowing a user manager to update a system admin's details such as email, first name and last name.

O3 Security · Impact-Aware SCA

Is GHSA-6xjj-v76v-fwpj in your dependencies?

O3 detects GHSA-6xjj-v76v-fwpj across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works