dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-58073

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 OAuth state.

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 · moderate confidence

Mattermost fails to properly validate the OAuth state parameter during team invitation, allowing attackers to bypass authorization checks and join any team on the server using manipulated OAuth state in conjunction with a valid invite token. This is an authorization bypass in the OAuth-based team join flow.

MitigationUpgrade Mattermost to versions 10.11.2, 10.10.3, or 10.5.11 or later. If immediate upgrade is not possible, restrict OAuth provider configuration and monitor for unauthorized team joins.

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` or access the system console > About > Mattermost and note the Server Version field
    Affected if The installed version falls within 10.5.0-10.5.10, 10.10.0-10.10.2, or 10.11.0-10.11.2
  2. Verify OAuth authentication is configured
    Check System Console > Authentication > OAuth 2.0 or review config.json for any enabled OAuth providers (GitLab, Google, Office 365, etc.)
    Affected if OAuth 2.0 providers are enabled and users can authenticate via OAuth to join the server
  3. Confirm team invitation system is in use
    Check System Console > User Management > Teams or inspect whether 'Allow anyone to join any team with an invite link' or 'By invitation only' settings are configured
    Affected if Team invitation links or invitation-only team settings are active, making the bypass relevant
  4. Review recent team membership audit logs
    Access System Console > Audit Logs and filter for events involving team join, invite token use, or OAuth authentication, looking for unauthorized team access
    Affected if Unusual team join events exist where users joined teams without proper invitation or outside expected invitation workflow

A user is affected if their Mattermost Server version is 10.5.0-10.5.10, 10.10.0-10.10.2, or 10.11.0-10.11.2 AND OAuth authentication is enabled AND team invitations are in use.

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 10.11.2, 10.10.3, or 10.5.11 or later. If immediate upgrade is not possible, restrict OAuth provider configuration and monitor for unauthorized team joins.

Recommended fix High confidence

Upgrade to 10.5.11, 10.10.3, or 10.11.3 depending on your current branch (10.5.x, 10.10.x, or 10.11.x)

  1. 1. Identify the currently installed Mattermost Server version by checking the system or Mattermost configuration
  2. 2. For Mattermost 10.5.x (versions 10.5.0 through 10.5.10): Upgrade to version 10.5.11
  3. 3. For Mattermost 10.10.x (versions 10.10.0 through 10.10.2): Upgrade to version 10.10.3
  4. 4. For Mattermost 10.11.x (versions 10.11.0 through 10.11.1): Upgrade to version 10.11.3
  5. 5. Before upgrading, review the Mattermost upgrade guide and take a complete backup of the database and configuration files
  6. 6. After upgrading, verify the OAuth configuration and team invite settings to ensure the authorization fix is working correctly
Caveat Check Mattermost release notes for your version branch for any breaking changes between your current version and the target fixed version

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
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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