dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2023-45316

HIGH · 8.8 CVSS v3.1 Published 2023-12-12
Fix available
A fix is available. Upgrade to after 9.2.1 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 fails to validate if a relative path is passed in /plugins/playbooks/api/v0/telemetry/run/<telem_run_id> as a telemetry run ID, allowing an attacker to use a path traversal payload that points to a different endpoint leading to a CSRF attack.

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 Playbooks plugin fails to validate the telemetry run ID parameter in /plugins/playbooks/api/v0/telemetry/run/<telem_run_id>. The endpoint accepts path traversal characters in the telem_run_id parameter without validation, allowing attackers to redirect requests to arbitrary internal endpoints and perform CSRF attacks.

MitigationImplement strict input validation on the telem_run_id parameter to reject path traversal sequences and ensure all state-changing endpoints require valid CSRF tokens.

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:<= 7.8.14>= 8.0.0, <= 8.1.5>= 9.0.0, <= 9.0.3>= 9.1.1, <= 9.1.2>= 9.2.0, <= 9.2.1

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
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Verify Mattermost Server version
    Check the server version through the system console or by querying the API endpoint /api/v4/system/config or using the mmctl command: mmctl --local config get Version
    Affected if The installed version falls within any of these ranges: <=7.8.14, 8.0.0-8.1.5, 9.0.0-9.0.3, 9.1.1-9.1.2, or 9.2.0-9.2.1
  2. Confirm Playbooks plugin is enabled
    Navigate to Product menu > Marketplace or go to /plugins/plugin_management to list installed plugins. Verify that the Playbooks plugin is installed and enabled.
    Affected if The Playbooks plugin is installed and enabled on the server
  3. Check for suspicious telemetry API access in logs
    Search server logs for requests to /plugins/playbooks/api/v0/telemetry/run/ containing path traversal sequences like ../ or %2e%2e. Review proxy and access logs for unusual patterns.
    Affected if Logs show requests to the telemetry endpoint with path traversal characters in the telem_run_id parameter
  4. Verify CSRF token enforcement on state-changing endpoints
    Test the telemetry endpoint with a crafted request containing path traversal in the telem_run_id parameter while omitting or providing an invalid CSRF token header.
    Affected if Requests to the telemetry endpoint succeed without requiring valid CSRF tokens in request headers

A user is affected if their Mattermost Server runs a version within the affected ranges AND has the Playbooks plugin enabled, as the vulnerability requires the plugin to be active.

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 9.2.1
Interim mitigation

Implement strict input validation on the telem_run_id parameter to reject path traversal sequences and ensure all state-changing endpoints require valid CSRF tokens.

Recommended fix Moderate confidence

Minimum: 7.8.15 (for 7.x), 8.1.6 (for 8.0.x), 9.0.4 (for 9.0.x), 9.1.3 (for 9.1.x) - or migrate to latest stable release

  1. 1. Identify your current Mattermost Server version by navigating to System Console > About or checking the server logs
  2. 2. For Mattermost 7.x users: Upgrade to version 7.8.15 or later
  3. 3. For Mattermost 8.0.x users: Upgrade to version 8.1.6 or later
  4. 4. For Mattermost 9.0.x users: Upgrade to version 9.0.4 or later
  5. 5. For Mattermost 9.1.x users: Upgrade to version 9.1.3 or later
  6. 6. After upgrade, verify the /plugins/playbooks/api/v0/telemetry/run/ endpoint properly validates and rejects path traversal attempts
Caveat Review Mattermost release notes for your target version for any breaking changes, particularly between major version upgrades (e.g., 7.x to 8.x, 8.x to 9.x)

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
18.0 hours of engineering $3,200
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-45316 — 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-2023-45316 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