CVE-2024-5272: Run Details leak to guest via webhook event "custom_playbooks_playbook_run_updated"

Published May 26, 2024
·
Updated

Mattermost versions 9.5.x <= 9.5.3, 9.6.x <= 9.6.1, 8.1.x <= 8.1.12 fail to restrict the audience of the "customplaybooksplaybookrunupdated" webhook event, which allows a guest on a channel with a playbook run linked to see all the details of the playbook run when the run is marked by finished.

Affected Software

4 affected components
Mattermost Mattermost<=9.5.3, <=9.6.1, <=8.1.12
Mattermost Mattermost Server>=8.1.0<8.1.13
Mattermost Mattermost Server>=9.5.0<9.5.4
Mattermost Mattermost Server>=9.6.0<9.6.2

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade Mattermost to a version that resolves this vulnerability.

    Fixed in 9.7.0
  2. Upgrade

    Upgrade Mattermost to a version that resolves this vulnerability.

    Fixed in 9.5.4
  3. Upgrade

    Upgrade Mattermost to a version that resolves this vulnerability.

    Fixed in 9.6.2
  4. Upgrade

    Upgrade Mattermost to a version that resolves this vulnerability.

    Fixed in 8.1.13

Event History

May 26, 2024
CVE Published
via MITRE·01:29 PM
Data Sourced
via MITRE·01:29 PM
RemedyDescriptionSeverityWeakness
Data Sourced
via NVD·02:15 PM
DescriptionSeverityWeaknessAffected Software

Frequently Asked Questions

1

What is the severity of CVE-2024-5272?

CVE-2024-5272 is rated as a high-severity vulnerability due to unauthorized access to sensitive playbook run details by guests.

2

How do I fix CVE-2024-5272?

To fix CVE-2024-5272, upgrade Mattermost to versions 9.5.4, 9.6.2, or later versions beyond 8.1.12.

3

What are the affected versions for CVE-2024-5272?

CVE-2024-5272 affects Mattermost versions 9.5.x up to 9.5.3, 9.6.x up to 9.6.1, and 8.1.x up to 8.1.12.

4

What is the impact of CVE-2024-5272?

The impact of CVE-2024-5272 allows guests in a channel to access all details of a linked playbook run, breaching confidentiality.

5

Is there a workaround for CVE-2024-5272?

There are no known workarounds for CVE-2024-5272, and upgrading to a patched version is the recommended solution.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203