How severe is GHSA-vpcr-fqpc-386h?

GHSA-vpcr-fqpc-386h has a CVSS score of 4/10, rated MEDIUM. Review your exposure and patch according to your risk tolerance.

Which packages are affected by GHSA-vpcr-fqpc-386h?

GHSA-vpcr-fqpc-386h affects the following packages: github.com/mattermost/mattermost-plugin-confluence (Go). Ecosystems affected: Go.

How do I fix GHSA-vpcr-fqpc-386h?

Update github.com/mattermost/mattermost-plugin-confluence to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vpcr-fqpc-386h is resolved across your whole dependency graph.

How do I detect GHSA-vpcr-fqpc-386h in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-plugin-confluence. 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-vpcr-fqpc-386h 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-vpcr-fqpc-386h?

O3 pinpoints whether GHSA-vpcr-fqpc-386h 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-vpcr-fqpc-386h actively exploited in the wild?

No public exploit code has been indexed for GHSA-vpcr-fqpc-386h 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-vpcr-fqpc-386h?

GHSA-vpcr-fqpc-386h is classified as CWE-862 (CWE-862). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was GHSA-vpcr-fqpc-386h published, and has it been updated?

GHSA-vpcr-fqpc-386h was published on August 11, 2025 and was last updated on August 18, 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

MEDIUM severity

GHSA-vpcr-fqpc-386h

MEDIUM

GHSA-vpcr-fqpc-386h is a medium-severity (CVSS 4) CWE-862 vulnerability in github.com/mattermost/mattermost-plugin-confluence. O3 Security confirms whether GHSA-vpcr-fqpc-386h is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

Mattermost Confluence Plugin has Missing Authorization vulnerability

Also known asCVE-2025-44001GO-2025-3863

Published

Aug 11, 2025

Updated

Aug 18, 2025

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Exploitation data as of Aug 18, 2025 · OSV.dev, NVD, FIRST.org (EPSS)

Real-World Exposure

1 pkg affected

🐹github.com/mattermost/mattermost-plugin-confluence

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 Confluence Plugin versions < 1.5.0 fail to check user access to the channel, which allows attackers to get channel subscription details without proper access to the channel via an API call to the Get Channel Subscriptions details endpoint.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/mattermost/mattermost-plugin-confluence`	all versions	1.5.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-plugin-confluence. 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-plugin-confluence to 1.5.0 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-vpcr-fqpc-386h 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-vpcr-fqpc-386h 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-vpcr-fqpc-386h. 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-vpcr-fqpc-386h in your dependencies?

O3 detects GHSA-vpcr-fqpc-386h 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