dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-58075

HIGH · 8.1 CVSS v3.1 Published 2025-10-16
Fix available
A fix is available. Upgrade to 10.5.11 / 10.10.3 or later.
See remediation →
87/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 10.11.x <= 10.11.1, 10.10.x <= 10.10.2, 10.5.x <= 10.5.10 fail to verify a user has permission to join a Mattermost team using the original invite token which allows any attacked to join any team on a Mattermost server regardless of restrictions via manipulating the RelayState

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 fails to verify user permissions when joining a team via the original invite token. The vulnerability allows attackers to bypass team join restrictions by manipulating the RelayState parameter, enabling unauthorized access to any team on the server.

MitigationUpgrade Mattermost to versions higher than 10.11.1, 10.10.2, and 10.5.10. Verify that team invite links properly enforce permission checks after patching.

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:>= 10.5.0, < 10.5.11>= 10.10.0, < 10.10.3>= 10.11.0, < 10.11.3

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
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/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. Determine Mattermost Server version
    Run 'mattermost version' from the command line, or access the System Console > About page, or query the /api/v4/system/analytics endpoint for 'version'
    Affected if Installed version falls within >= 10.5.0 < 10.5.11, >= 10.10.0 < 10.10.3, or >= 10.11.0 < 10.11.3
  2. Check if SAML authentication is enabled
    Access System Console > Authentication > SAML 2.0, or inspect the config.json file for 'SamlSettings' with 'Enable' set to true
    Affected if SAML authentication is enabled and the server version is in the affected range
  3. Verify team invitation settings
    Access System Console > Team Settings > Allow any user with an account on this server to join any team, or inspect the team settings in the database
    Affected if Team invitation is permitted and the server version is in the affected range

If the Mattermost Server version is within the affected ranges (10.5.0-10.5.10, 10.10.0-10.10.2, or 10.11.0-10.11.2) AND SAML authentication or team invites are in use, the environment is likely vulnerable to unauthorized team access via manipulated invite tokens.

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 10.5.11 / 10.10.3 / 10.11.3 or later
Fixed in 10.5.1110.10.310.11.3
Interim mitigation

Upgrade Mattermost to versions higher than 10.11.1, 10.10.2, and 10.5.10. Verify that team invite links properly enforce permission checks after patching.

Recommended fix High confidence

Mattermost Server 10.5.11, 10.10.3, 10.11.3 or later

  1. Identify the current Mattermost Server version from the system console or by running 'mmctl version'
  2. Determine the appropriate upgrade path: for 10.5.x upgrade to 10.5.11+, for 10.10.x upgrade to 10.10.3+, for 10.11.x upgrade to 10.11.3+
  3. Review the Mattermost upgrade documentation at https://docs.mattermost.com/upgrade/upgrading-mattermost-server.html
  4. Back up the Mattermost database and configuration files before proceeding
  5. Stop the Mattermost server service
  6. Install the fixed version (10.5.11, 10.10.3, or 10.11.3 or later) using the appropriate installation method for your environment
  7. Start the Mattermost server and verify the service is running correctly
  8. Test that the team invitation flow now properly enforces authorization checks for invite tokens

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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