CVE-2025-47871
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedMattermost versions 10.5.x <= 10.5.5, 9.11.x <= 9.11.15, 10.8.x <= 10.8.0, 10.7.x <= 10.7.2, 10.6.x <= 10.6.5 fail to properly validate channel membership when retrieving playbook run metadata, allowing authenticated users who are playbook members but not channel members to access sensitive information about linked private channels including channel name, display name, and participant count through the run metadata API endpoint.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceMattermost fails to properly validate channel membership in the playbook run metadata API endpoint. Authenticated users who are playbook members but NOT members of a linked private channel can retrieve sensitive metadata (channel name, display name, participant count) about that private channel through the run metadata API, leading to unauthorized information disclosure.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data>= 9.11.0, < 9.11.16>= 10.5.0, < 10.5.6>= 10.6.0, < 10.6.6>= 10.7.0, < 10.7.3= 10.8.0CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Check Mattermost Server versionAccess the Mattermost System Console > About or run `grep Version /opt/mattermost/config/config.json` or check the Mattermost version via the system console. You can also use the API: GET /api/v4/system/publicAffected if The installed version falls within one of these ranges: 9.11.0 to 9.11.15, 10.5.0 to 10.5.5, 10.6.0 to 10.6.5, 10.7.0 to 10.7.2, or exactly 10.8.0
-
Verify Playbooks plugin is enabledNavigate to System Console > Plugins > Plugin Management, or query the API at GET /api/v4/pluginsAffected if The Playbooks plugin is installed and enabled
-
Identify playbooks with linked private channelsQuery the Playbooks API: GET /api/v1/playbooks to list playbooks, then for each playbook check the channel_id field. Cross-reference channel IDs with private channels using GET /api/v4/channels/{channel_id} and checking the type field equals 'P' for private channelsAffected if There exist playbooks linked to private channels where the requesting user is a playbook member but not a member of the linked private channel
-
Test run metadata API for unauthorized disclosureAs an authenticated user who is a member of a playbook but NOT a member of its linked private channel, make a request to GET /api/v1/playbooks/runs/{run_id}/metadata and inspect the response for the channel field containing private channel details (name, display_name, participant_count)Affected if The API response returns channel metadata (channel name, display name, participant count) for a private channel the requesting user is not a member of
If the Mattermost Server version is in the affected list AND the Playbooks plugin is enabled AND there are playbooks linked to private channels, then the environment is vulnerable to unauthorized information disclosure through the run metadata API.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped9.11.1610.5.610.6.6
Upgrade to Mattermost versions 10.5.6+, 9.11.16+, 10.8.1+, 10.7.3+, 10.6.6+ (or later patched versions) which include proper channel membership validation in the run metadata API endpoint.
9.11.16, 10.5.6, 10.6.6, or 10.7.3 depending on your current release branch
- 1. Identify current Mattermost Server version by accessing the system console or checking the /about API endpoint
- 2. Determine the appropriate target version based on your current major.minor release: 9.11.x users should upgrade to 9.11.16; 10.5.x users should upgrade to 10.5.6; 10.6.x users should upgrade to 10.6.6; 10.7.x users should upgrade to 10.7.3
- 3. Create a complete backup of the Mattermost database and config file before upgrading
- 4. Test the upgrade in a staging or test environment first
- 5. Schedule a maintenance window for the production upgrade
- 6. Follow Mattermost upgrade documentation to apply the server update
- 7. After upgrade, verify that authenticated playbook members can no longer access private channel metadata they are not members of
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47871 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-47871 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data