dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2024-41144

HIGH · 7.1 CVSS v3.1 Published 2024-08-01
Fix available
A fix is available. Upgrade to 9.5.7 / 9.7.6 or later.
See remediation →
77/100
Remediation priority · High
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 versions 9.9.x <= 9.9.0, 9.5.x <= 9.5.6, 9.7.x <= 9.7.5, 9.8.x <= 9.8.1 fail to properly validate synced posts, when shared channels are enabled,  which allows a malicious remote to create/update/delete arbitrary posts in arbitrary channels

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

Mattermost versions 9.9.x, 9.5.x, 9.7.x, and 9.8.x fail to properly validate synced posts when shared channels are enabled. A malicious remote instance connected via shared channels can bypass authorization checks to create, update, or delete arbitrary posts in any channel on the local Mattermost instance.

MitigationUpgrade Mattermost to versions 9.9.1, 9.5.7, 9.7.6, or 9.8.2 or later. Alternatively, disable the shared channels feature if upgrade is not immediately possible.

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
Mattermost ServerApplication
Affected:>= 9.5.0, < 9.5.7>= 9.7.0, < 9.7.6>= 9.8.0, < 9.8.2= 9.9.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
None
Integrity
High
Availability
Low

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

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. Check installed Mattermost Server version
    Run 'mattermost server version' or check the System Console > About page for the version number
    Affected if Version is 9.5.0 through 9.5.6, 9.7.0 through 9.7.5, 9.8.0 through 9.8.1, or exactly 9.9.0
  2. Verify if shared channels feature is enabled
    Navigate to System Console > Shared Channels or check the 'SharedChannels' configuration setting in config.json
    Affected if Shared channels feature is turned ON (enabled)
  3. Check for active shared channel connections
    Navigate to System Console > Shared Channels > Remote Clusters to list all remote instances connected via shared channels
    Affected if One or more remote instances are connected via shared channels

If the installed version falls within the affected ranges (9.5.0-9.5.6, 9.7.0-9.7.5, 9.8.0-9.8.1, or 9.9.0) AND shared channels are enabled with at least one remote instance connected, the local instance is vulnerable to unauthorized post manipulation by the remote attacker.

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 9.5.7 / 9.7.6 / 9.8.2 or later
Fixed in 9.5.79.7.69.8.2
Interim mitigation

Upgrade Mattermost to versions 9.9.1, 9.5.7, 9.7.6, or 9.8.2 or later. Alternatively, disable the shared channels feature if upgrade is not immediately possible.

Recommended fix High confidence

Upgrade to 9.5.7 (if on 9.5.x), 9.7.6 (if on 9.7.x), 9.8.2 (if on 9.8.x), or 9.9.1 or later (if on 9.9.x)

  1. 1. Identify the currently running Mattermost Server version using the system console or mmctl command
  2. 2. Determine the appropriate upgrade path based on your current version (see upgrade_path)
  3. 3. Back up your Mattermost database and configuration files before upgrading
  4. 4. Download the fixed version of Mattermost Server from the official Mattermost download page
  5. 5. Stop the Mattermost service
  6. 6. Install the upgraded version following Mattermost upgrade documentation
  7. 7. Verify the upgrade was successful by checking the version in the system console
  8. 8. Confirm that shared channels functionality works as expected post-upgrade
Caveat Review Mattermost release notes for your target version as minor releases may include deprecations or configuration changes

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
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,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-41144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2024-41144 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