PlaybooksApplication · Mattermost

CVE-2022-1548

HIGH · 8.8 CVSS v3.1 Published 2022-05-03
Fix available
A fix is available. Upgrade to after 1.25.0 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable Zero-click

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 · unedited
Mattermost Playbooks plugin 1.25 and earlier fails to properly restrict user-level permissions, which allows playbook members to escalate their membership privileges and perform actions restricted to playbook admins.

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 confidence

The Mattermost Playbooks plugin versions 1.25 and earlier contains a broken access control vulnerability where permission checks are not properly enforced. This allows playbook members (standard users with limited privileges) to escalate their access and perform actions that should be restricted to playbook administrators, such as modifying playbook settings, managing runs, or accessing sensitive configurations.

MitigationUpgrade Mattermost Playbooks plugin to version 1.26 or later which contains the patched permission validation logic. As a temporary compensating control, audit existing playbook memberships and restrict admin-level actions until the upgrade can be applied.

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
PlaybooksApplication
Affected:<= 1.25.0

CVSS 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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Mattermost Playbooks plugin version
    Access the Mattermost System Console and navigate to the Plugin Management section. Locate the Playbooks plugin and note its installed version number.
    Affected if The installed version is 1.25.0 or any earlier version (e.g., 1.24.x, 1.23.x, etc.)
  2. Confirm plugin is enabled
    In the Plugin Management section of the Mattermost System Console, verify that the Playbooks plugin shows an Active status.
    Affected if The plugin is enabled and the version is 1.25.0 or earlier.
  3. Review playbook membership assignments
    Access individual playbooks through the Playbooks UI. For each playbook, examine the Members list to identify standard users (non-admin) who have been granted access.
    Affected if Standard users are present as playbook members in any playbook.
  4. Audit recent playbook configuration changes
    Review the audit logs or playbook change history for modifications to playbook settings (such as default reminders, export settings, or webhook configurations) performed by users who should not have admin-level access.
    Affected if Any configuration changes were made by users who are not designated as playbook administrators.

A user is affected if the Mattermost Playbooks plugin version is 1.25.0 or earlier and standard users have access to playbooks that may have been modified beyond their intended privileges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to a release after 1.25.0
Interim mitigation

Upgrade Mattermost Playbooks plugin to version 1.26 or later which contains the patched permission validation logic. As a temporary compensating control, audit existing playbook memberships and restrict admin-level actions until the upgrade can be applied.

Recommended fix Moderate confidence

Playbooks plugin version 1.25.1 or later

  1. Upgrade the Mattermost Playbooks plugin to a version greater than 1.25.0 (e.g., 1.25.1 or later)

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Playbooks Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing8.0 h
  • Review / QA4.0 h
18.0 hours of engineering $3,080
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,928.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-1548 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-1548 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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