How severe is GHSA-fqrq-xmxj-v47x?

GHSA-fqrq-xmxj-v47x has a CVSS score of 4.3/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-fqrq-xmxj-v47x?

GHSA-fqrq-xmxj-v47x affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-fqrq-xmxj-v47x?

Update github.com/mattermost/mattermost/server/v8 to 9.11.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fqrq-xmxj-v47x is resolved across your whole dependency graph.

How do I detect GHSA-fqrq-xmxj-v47x 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/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.

How do I mitigate GHSA-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x?

O3 pinpoints whether GHSA-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x actively exploited in the wild?

No public exploit code has been indexed for GHSA-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x?

GHSA-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x published, and has it been updated?

GHSA-fqrq-xmxj-v47x was published on March 19, 2025 and was last updated on March 25, 2025. 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-fqrq-xmxj-v47x

MEDIUM

GHSA-fqrq-xmxj-v47x is a medium-severity (CVSS 4.3) CWE-863 vulnerability in github.com/mattermost/mattermost/server/v8. O3 Security confirms whether GHSA-fqrq-xmxj-v47x is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Fails to Properly Perform Viewer Role Authorization

Also known asCVE-2025-1472GO-2025-3534

Published

Mar 19, 2025

Updated

Mar 25, 2025

Affected

2 pkgs

Patched

2 / 2

Exploits

None indexed

Blast Radius

2 pkgs affected

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

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 versions 9.11.x <= 9.11.8 fail to properly perform authorization of the Viewer role which allows an attacker with the Viewer role configured with No Access to Reporting to still view team and site statistics.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.11.0&&< 9.11.9	9.11.9
🐹Go	`github.com/mattermost/mattermost-server`	≥ 9.11.0&&< 9.11.9	9.11.9

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/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 9.11.9 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x 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-fqrq-xmxj-v47x. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is GHSA-fqrq-xmxj-v47x in your dependencies?

O3 detects GHSA-fqrq-xmxj-v47x 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