CVE-2025-46702
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 enforce channel member management permissions when adding participants to playbook runs. This allows authenticated users with member-level permissions to bypass system admin restrictions and add or remove users to/from private channels via the playbook run participants feature, even when the 'Manage Members' permission has been explicitly removed. This can lead to unauthorized access to sensitive channel content and allow guest users to gain channel management privileges.
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 enforce channel member management permissions when adding participants to playbook runs, allowing authenticated member-level users to bypass admin-set 'Manage Members' restrictions and add/remove users from private channels. This enables unauthorized access to sensitive channel content and grants guest users improper channel management privileges.
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.
-
Identify Mattermost Server versionRun 'sudo mattermost version' or check the System Console > About page for the exact version numberAffected if Version matches: >= 9.11.0 and < 9.11.16; OR >= 10.5.0 and < 10.5.6; OR >= 10.6.0 and < 10.6.6; OR >= 10.7.0 and < 10.7.3; OR = 10.8.0
-
Verify Playbooks plugin is enabledNavigate to System Console > Plugins > Plugin Management, or check /opt/mattermost/plugins directory for the 'playbooks' plugin folder; alternatively, run 'mattermost plugin list' CLI commandAffected if Playbooks plugin is installed and enabled (vulnerability exists in the playbook run participants feature)
-
Confirm custom channel member permissions are configuredCheck System Console > User Management > Roles for any custom roles, or inspect a private channel's permissions via channel menu > Manage Members to see if 'Manage Members' is restricted to admins onlyAffected if Admin has configured restrictions on 'Manage Members' permission that should block member-level users from adding/removing participants
-
Audit guest and member role assignmentsNavigate to System Console > User Management > Users and review which users have 'Guest' role or standard 'Member' role, particularly those with access to private channels containing sensitive contentAffected if Guest users or member-level users exist in private channels where they should not have participant management privileges
You are affected if your Mattermost Server version falls within any of the affected ranges AND the Playbooks plugin is enabled, as the vulnerability allows authenticated member-level users to bypass channel member management restrictions when adding participants to playbook runs.
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 Mattermost to versions 10.5.6+, 9.11.16+, 10.8.1+, 10.7.3+, 10.6.6+ (or later) to patch the permission bypass in the playbook run participants feature.
Upgrade to the latest patch version for your branch: 9.11.16, 10.5.6, 10.6.6, or 10.7.3
- 1. Identify the current Mattermost Server version by checking the system console or running 'mattermost version'
- 2. Determine which version branch your current installation belongs to (9.11.x, 10.5.x, 10.6.x, or 10.7.x)
- 3. For 9.11.x versions: Upgrade to version 9.11.16
- 4. For 10.5.x versions: Upgrade to version 10.5.6
- 5. For 10.6.x versions: Upgrade to version 10.6.6
- 6. For 10.7.x versions: Upgrade to version 10.7.3
- 7. Follow standard Mattermost upgrade procedures: back up the database and config file, stop the server, install the new version, restart the server
- 8. Verify the upgrade was successful and test that the playbook run participants feature now properly enforces channel member management permissions
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation2.0 h
- Testing3.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 $2,832.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-46702 — 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-46702 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