dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-2475

MEDIUM · 5.4 CVSS v3.1 Published 2025-04-14
Fix available
A fix is available. Upgrade to 9.11.10 / 10.4.4 or later.
See remediation →
60/100
Remediation priority · Elevated
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.5.x <= 10.5.1, 10.4.x <= 10.4.3, 9.11.x <= 9.11.9 fail to invalidate the cache when a user account is converted to a bot which allows an attacker to login to the bot exactly one time via normal credentials.

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 invalidate authentication cache when user accounts are converted to bot accounts, causing stale session data to persist. This allows an attacker to authenticate using the original user's credentials exactly once after the conversion, exploiting the gap between account type change and cache invalidation.

MitigationUpgrade to Mattermost 10.5.2+, 10.4.4+, or 9.11.10+ to receive the patch, or ensure manual cache invalidation is performed immediately after any user-to-bot conversions.

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.10>= 10.4.0, < 10.4.4>= 10.5.0, < 10.5.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/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. Check installed Mattermost Server version
    Run the command: grep -i version /opt/mattermost/config/config.json or use the Mattermost system console to view server version under About > Mattermost
    Affected if The version falls within 9.11.0 to 9.11.9, 10.4.0 to 10.4.3, or 10.5.0 to 10.5.1
  2. Review audit logs for user-to-bot conversions
    Access Mattermost audit logs via the System Console or check /var/log/mattermost/audit.log for events containing 'user_to_bot' or similar conversion actions, or query the database for accounts where account_type changed from User to Bot
    Affected if Any user-to-bot account conversions have occurred and the server version is vulnerable
  3. Identify bot accounts derived from user accounts
    Query the Users table and Bots table in the Mattermost database to identify bot accounts that share the same username or email as previously existing user accounts, or review the audit log for 'createBot' events following 'updateUser' events
    Affected if Bot accounts exist that were converted from user accounts after the vulnerable version was installed
  4. Check for stale sessions from converted accounts
    Query the Sessions table in the Mattermost database for active sessions belonging to usernames that now exist only as bot accounts, or use the Mattermost CLI: mattermost user list sessions --user <username> for affected accounts
    Affected if Active sessions exist for accounts that were converted to bots, indicating the authentication cache was not invalidated

A user is affected if the Mattermost Server version is in the vulnerable range AND any user accounts have been converted to bot accounts, as stale sessions may still 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 9.11.10 / 10.4.4 / 10.5.2 or later
Fixed in 9.11.1010.4.410.5.2
Interim mitigation

Upgrade to Mattermost 10.5.2+, 10.4.4+, or 9.11.10+ to receive the patch, or ensure manual cache invalidation is performed immediately after any user-to-bot conversions.

Recommended fix Moderate confidence

Upgrade to 9.11.10, 10.4.4, or 10.5.2 (whichever corresponds to your current major.minor branch)

  1. Determine your current Mattermost Server version by checking the system console or running 'mattermost version'
  2. Stop the Mattermost Server service
  3. Backup your Mattermost database and configuration files
  4. For version 9.11.x: Upgrade to version 9.11.10 or later
  5. For version 10.4.x: Upgrade to version 10.4.4 or later
  6. For version 10.5.x: Upgrade to version 10.5.2 or later
  7. Verify the upgrade by checking the Mattermost Server version after restart
  8. Ensure the server starts successfully and test user authentication

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
  • Testing3.0 h
  • Review / QA2.0 h
12.0 hours of engineering $2,130
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,408.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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