How severe is GHSA-wp43-vprh-c3w5?

GHSA-wp43-vprh-c3w5 has a CVSS score of 6.5/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-wp43-vprh-c3w5?

GHSA-wp43-vprh-c3w5 affects the following packages: github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go), github.com/mattermost/mattermost/server/v8 (Go). Ecosystems affected: Go.

How do I fix GHSA-wp43-vprh-c3w5?

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

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

How do I mitigate GHSA-wp43-vprh-c3w5 if there is no patch (or I can't update yet)?

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.

Is GHSA-wp43-vprh-c3w5 actively exploited in the wild?

No public exploit code has been indexed for GHSA-wp43-vprh-c3w5 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-wp43-vprh-c3w5?

GHSA-wp43-vprh-c3w5 has an EPSS (Exploit Prediction Scoring System) score of 0.2%, placing it in the 13th 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-wp43-vprh-c3w5?

GHSA-wp43-vprh-c3w5 is classified as CWE-284 (CWE-284), CWE-346 (CWE-346). These weakness types describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-wp43-vprh-c3w5 published, and has it been updated?

GHSA-wp43-vprh-c3w5 was published on April 5, 2024 and was last updated on December 16, 2024. 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

MEDIUM severity

Mattermost fails to authenticate the source of certain types of post actionsGHSA-wp43-vprh-c3w5

MEDIUM

GHSA-wp43-vprh-c3w5 is a medium-severity (CVSS 6.5) CWE-284 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.

Also known asBIT-mattermost-2024-2447CVE-2024-2447GO-2024-2696

Published

Apr 5, 2024

Updated

Dec 16, 2024

Affected

4 pkgs

Patched

4 / 4

Exploits

None indexed

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

Exploitation Status

No confirmed exploitation observed yet

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 GHSA-wp43-vprh-c3w5.

EPSS Exploitation Probability

via FIRST.org ↗

0.2%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs13th percentile — riskier than 13% of all scored CVEsHighest risk

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

4 pkgs affected

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

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 8.1.x before 8.1.11, 9.3.x before 9.3.3, 9.4.x before 9.4.4, and 9.5.x before 9.5.2 fail to authenticate the source of certain types of post actions, allowing an authenticated attacker to create posts as other users via a crafted post action.

Affected Packages

4 total 4 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 8.1.0&&< 8.1.11	8.1.11`go get github.com/mattermost/mattermost/server/v8@v8.1.11`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.5.0&&< 9.5.2	9.5.2`go get github.com/mattermost/mattermost/server/v8@v9.5.2`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.4.0&&< 9.4.4	9.4.4`go get github.com/mattermost/mattermost/server/v8@v9.4.4`
🐹Go	`github.com/mattermost/mattermost/server/v8`	≥ 9.3.0&&< 9.3.3	9.3.3`go get github.com/mattermost/mattermost/server/v8@v9.3.3`

Affected Products

1 product · 4 configurations

Application

mattermost servermattermost

≥ 9.5.0 && < 9.5.2

range

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, 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 8.1.11 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-wp43-vprh-c3w5 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

O3 Security · Impact-Aware SCA

Is GHSA-wp43-vprh-c3w5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works

CVSS Score

6.5/10CVSS v3 base

Vector breakdown

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

None

Integrity

High

Availability

None

Raw vector

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N

CWE Classification

CWE-284CWE-284 CWE-346CWE-346

Weaponization

No Nuclei template, Metasploit module or public proof-of-concept found.

Timeline

Disclosed

Apr 5, 2024

Last updated

Dec 16, 2024

Identifiers

GHSA-wp43-vprh-c3w5

BIT-mattermost-2024-2447

GO-2024-2696

References

Advisorynvd.nist.gov · CVE 2024 2447 Webmattermost.com · security updates Packagemattermost/mattermost

Related vulnerabilities

This CVE is medium severity; 7 of 8 other CVEs affecting v8 are rated as high or higher (top: high).

CVE-2026-8823CVE-2026-6046CVE-2026-7387CVE-2026-6961CVE-2026-7184CVE-2026-6689CVE-2026-6739CVE-2026-3433

Provenance

Sources

OSV.devNVDFIRST.org (EPSS)

Last verifiedDec 16, 2024

Mattermost fails to authenticate the source of certain types of post actionsGHSA-wp43-vprh-c3w5

Exploitation Status

No confirmed exploitation observed yet

EPSS Exploitation Probability

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

Description

Affected Packages

Affected Products

Detection & mitigation playbook

Detect

Fix

Workarounds

Frequently Asked Questions

Is GHSA-wp43-vprh-c3w5 in your dependencies?