Skip to content

Mattermost Playbooks fails to properly validate permissions

Low severity GitHub Reviewed Published Apr 24, 2025 to the GitHub Advisory Database • Updated Apr 24, 2025

Package

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

Affected versions

>= 2.0.0, < 2.1.1
< 1.41.0

Patched versions

1.41.0
gomod github.com/mattermost/mattermost/server/v8 (Go)
< 8.0.0-20250218121836-2b5275d87136
>= 10.4.0, < 10.4.3
>= 10.5.0, < 10.5.1
>= 9.11.0, < 9.11.11
8.0.0-20250218121836-2b5275d87136

Description

Mattermost versions 10.4.x <= 10.4.2, 10.5.x <= 10.5.0, 9.11.x <= 9.11.10 fail to properly validate permissions for the API endpoint /plugins/playbooks/api/v0/signal/keywords/ignore-thread, allowing any user or attacker to delete posts containing actions created by the Playbooks bot, even without channel access or appropriate permissions.

References

Published by the National Vulnerability Database Apr 24, 2025
Published to the GitHub Advisory Database Apr 24, 2025
Reviewed Apr 24, 2025
Last updated Apr 24, 2025

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

Weaknesses

CVE ID

CVE-2025-41423

GHSA ID

GHSA-fr22-5377-f3p7

Source code

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