dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-25279

HIGH · 7.5 CVSS v3.1 Published 2025-02-24
Fix available
A fix is available. Upgrade to 9.11.8 / 10.2.3 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges 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 10.4.x <= 10.4.1, 9.11.x <= 9.11.7, 10.3.x <= 10.3.2, 10.2.x <= 10.2.2 fail to properly validate board blocks when importing boards which allows an attacker could read any arbitrary file on the system via importing and exporting a specially crafted import archive in Boards.

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

This is a path traversal vulnerability in Mattermost's Boards feature. When importing board archives, the application fails to properly validate board block paths, allowing an attacker to craft a malicious archive containing path traversal sequences (e.g., ../../../etc/passwd) to read arbitrary files from the server's filesystem.

MitigationUpgrade Mattermost to versions 10.4.2, 9.11.8, 10.3.3, or 10.2.3 and later. Until upgraded, restrict board import permissions to trusted users only.

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.11.0, < 9.11.8>= 10.2.0, < 10.2.3>= 10.3.0, < 10.3.3>= 10.4.0, < 10.4.2

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

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

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 the Mattermost Server version
    Access the system administration console and navigate to the About section, or use the mattermost version CLI command if available, to determine the exact installed version of Mattermost Server.
    Affected if The installed version is 9.11.0 through 9.11.7, 10.2.0 through 10.2.2, 10.3.0 through 10.3.2, or 10.4.0 through 10.4.1 (any version matching the pattern >=9.11.0 <9.11.8, >=10.2.0 <10.2.3, >=10.3.0 <10.3.3, or >=10.4.0 <10.4.2).
  2. Confirm the Boards plugin is enabled
    In the Mattermost admin console, navigate to the Plugins section and verify that the Boards plugin (focalboard) is installed and enabled.
    Affected if The Boards plugin is active on the server.
  3. Verify board import permission settings
    In the admin console, review the permissions configuration for the Boards plugin. Check which user roles or groups have permission to import board archives. This is typically found under Plugin -> Boards -> Permissions or within the Boards workspace settings.
    Affected if Users other than trusted administrators have the ability to import board archives, particularly if guest users or unauthenticated access is permitted.
  4. Inspect recent board import activity
    Review server logs for any board archive import operations. Look for patterns in file paths that may indicate path traversal attempts, or correlate import events with user activity logs.
    Affected if Board import functionality has been used, particularly if the server version is within the affected ranges.

A server is affected if it runs a Mattermost Server version within the affected ranges AND has the Boards plugin enabled with board import permissions available to users who could craft malicious archives.

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.11.8 / 10.2.3 / 10.3.3 or later
Fixed in 9.11.810.2.310.3.3
Interim mitigation

Upgrade Mattermost to versions 10.4.2, 9.11.8, 10.3.3, or 10.2.3 and later. Until upgraded, restrict board import permissions to trusted users only.

Recommended fix High confidence

Upgrade to the appropriate version: 9.11.8, 10.2.3, 10.3.3, or 10.4.2 (or later) based on your current major version branch

  1. 1. Backup your Mattermost Server database and configuration files before proceeding.
  2. 2. Ensure you have a rollback plan in case of issues.
  3. 3. For Mattermost Server 9.11.x: Upgrade to version 9.11.8 or later.
  4. 4. For Mattermost Server 10.2.x: Upgrade to version 10.2.3 or later.
  5. 5. For Mattermost Server 10.3.x: Upgrade to version 10.3.3 or later.
  6. 6. For Mattermost Server 10.4.x: Upgrade to version 10.4.2 or later.
  7. 7. Use your system's package manager or official Mattermost upgrade procedure (e.g., mattermostctl or the appropriate upgrade script for your deployment).
  8. 8. After upgrade, verify the server starts successfully and test the Boards functionality.
Caveat Review Mattermost release notes for your target version for any breaking changes or required migration steps

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
  • Testing6.0 h
  • Review / QA3.0 h
21.0 hours of engineering $3,680
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,888.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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