How severe is GHSA-g3f3-p9rc-775p?

No CVSS score has been assigned to GHSA-g3f3-p9rc-775p yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by GHSA-g3f3-p9rc-775p?

GHSA-g3f3-p9rc-775p affects the following packages: github.com/mattermost/mattermost-server (Go). Ecosystems affected: Go.

How do I fix GHSA-g3f3-p9rc-775p?

Update github.com/mattermost/mattermost-server to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3f3-p9rc-775p is resolved across your whole dependency graph.

How do I detect GHSA-g3f3-p9rc-775p 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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate GHSA-g3f3-p9rc-775p 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-g3f3-p9rc-775p?

O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g3f3-p9rc-775p can be triaged on real exposure rather than presence alone.

Is GHSA-g3f3-p9rc-775p actively exploited in the wild?

No public exploit code has been indexed for GHSA-g3f3-p9rc-775p 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 is the EPSS score for GHSA-g3f3-p9rc-775p?

GHSA-g3f3-p9rc-775p has an EPSS (Exploit Prediction Scoring System) score of 0.7%, placing it in the 50th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is GHSA-g3f3-p9rc-775p?

GHSA-g3f3-p9rc-775p is classified as CWE-732 (CWE-732). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-g3f3-p9rc-775p published, and has it been updated?

GHSA-g3f3-p9rc-775p was published on May 24, 2022 and was last updated on November 5, 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

Not in CISA KEV

GHSA-g3f3-p9rc-775p — mattermost-server

Fix: mattermost/mattermost@6c75662

GHSA-g3f3-p9rc-775p is a CWE-732 vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.

Mattermost Server exposes account details to any Team Administrator

Also known asCVE-2016-11080GO-2025-4063

Published

May 24, 2022

Updated

Nov 5, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Sep 20, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

0.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs50th percentile — riskier than 50% of all scored CVEsHighest risk

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Real-World Exposure

1 pkg affected

🐹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

An issue was discovered in Mattermost Server before 3.0.0. It offers superfluous APIs for a Team Administrator to view account details.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-server`	all versions	3.0.0`go get github.com/mattermost/mattermost-server@v3.0.0`

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 3.0.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-g3f3-p9rc-775p 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 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like GHSA-g3f3-p9rc-775p can be triaged on real exposure rather than presence alone.

Tailored to GHSA-g3f3-p9rc-775p. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

An issue was discovered in Mattermost Server before 3.0.0. It offers superfluous APIs for a Team Administrator to view account details.

O3 Security · Impact-Aware SCA

Is GHSA-g3f3-p9rc-775p in your dependencies?

O3 Security finds GHSA-g3f3-p9rc-775p across Go dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

Scan my dependencies How O3 SCA works