Skip to content

Mattermost doesn't check if {{team_id}} was being changed when updating playbooks

Low severity GitHub Reviewed Published May 18, 2026 to the GitHub Advisory Database • Updated Jun 1, 2026

Package

gomod github.com/mattermost/mattermost-plugin-playbooks (Go)

Affected versions

< 1.41.1-0.20260213020129-e1d6ec2c94e6

Patched versions

1.41.1-0.20260213020129-e1d6ec2c94e6
gomod github.com/mattermost/mattermost/server/v8 (Go)
>= 11.5.0, < 11.5.2
>= 10.11.0, < 10.11.14
11.5.2
10.11.14

Description

Mattermost versions 11.5.x <= 11.5.1, 10.11.x <= 10.11.13 fail to check if {{team_id}} was being changed when updating playbooks, allowing users with only {{Manage Playbook Configurations}} permission to change a playbook's team, bypassing manage members restriction via PUT api. Mattermost Advisory ID: MMSA-2025-00552

References

Published by the National Vulnerability Database May 18, 2026
Published to the GitHub Advisory Database May 18, 2026
Reviewed Jun 1, 2026
Last updated Jun 1, 2026

Severity

Low

CVSS overall score

This score calculates overall vulnerability severity from 0 to 10 and is based on the Common Vulnerability Scoring System (CVSS).
/ 10

CVSS v3 base metrics

Attack vector
Network
Attack complexity
High
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
Low
Availability
None

CVSS v3 base metrics

Attack vector: More severe the more the remote (logically and physically) an attacker can be in order to exploit the vulnerability.
Attack complexity: More severe for the least complex attacks.
Privileges required: More severe if no privileges are required.
User interaction: More severe when no user interaction is required.
Scope: More severe when a scope change occurs, e.g. one vulnerable component impacts resources in components beyond its security scope.
Confidentiality: More severe when loss of data confidentiality is highest, measuring the level of data access available to an unauthorized user.
Integrity: More severe when loss of data integrity is the highest, measuring the consequence of data modification possible by an unauthorized user.
Availability: More severe when the loss of impacted component availability is highest.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:N/I:L/A:N

EPSS score

Exploit Prediction Scoring System (EPSS)

This score estimates the probability of this vulnerability being exploited within the next 30 days. Data provided by FIRST.
(4th percentile)

Weaknesses

Incorrect Authorization

The product performs an authorization check when an actor attempts to access a resource or perform an action, but it does not correctly perform the check. Learn more on MITRE.

CVE ID

CVE-2026-4286

GHSA ID

GHSA-gvg4-jhmr-6j23

Source code

Loading Checking history
See something to contribute? Suggest improvements for this vulnerability.