dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-1412

HIGH · 8.8 CVSS v3.1 Published 2025-02-24
Fix available
A fix is available. Upgrade to 9.11.7 / 10.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
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 9.11.x <= 9.11.6, 10.4.x <= 10.4.1 fail to invalidate all active sessions when converting a user to a bot, with allows the converted user to escalate their privileges depending on the permissions granted to the bot.

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

In Mattermost versions 9.11.x through 9.11.6 and 10.4.x through 10.4.1, the user-to-bot conversion functionality does not properly invalidate existing sessions for the converted user account. This allows the original user session to persist after conversion, enabling the user to retain access and potentially escalate privileges based on the permissions assigned to the bot role.

MitigationUpgrade Mattermost to version 9.11.7 or later for 9.x branches, or version 10.4.2 or later for 10.x branches to ensure sessions are properly invalidated during user-to-bot conversion.

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

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/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. Check installed Mattermost Server version
    Run 'sudo mattermost version' or look in the system console under About > Mattermost, or check the /opt/mattermost/version file
    Affected if Version is 9.11.0 through 9.11.6 OR 10.4.0 through 10.4.1
  2. Identify bot accounts created via user conversion
    Query the database: SELECT id, username, createat FROM bots WHERE createat > 0 AND userid IS NOT NULL; or check the system console under Bot Accounts for bots that originated from converted user accounts
    Affected if Any bot accounts exist that were converted from regular user accounts using the user-to-bot conversion feature
  3. Check for active sessions tied to converted bot accounts
    Query the database: SELECT * FROM sessions WHERE userid IN (SELECT userid FROM bots WHERE userid IS NOT NULL); or inspect the system console under Session ID to see active sessions
    Affected if Active sessions exist for accounts that were converted from users to bots, indicating the session was not invalidated after conversion
  4. Verify session invalidation on recent conversions
    Review application logs for entries containing 'user' and 'bot' and 'convert' or 'session' around the time of user-to-bot conversions; check if 'session invalidated' messages are missing after conversion events
    Affected if Conversions occurred but no session termination is logged for the converted user account

You are affected if your Mattermost Server version falls within 9.11.0-9.11.6 or 10.4.0-10.4.1 AND you have used the user-to-bot conversion feature, with active sessions still present for converted accounts.

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.7 / 10.4.2 or later
Fixed in 9.11.710.4.2
Interim mitigation

Upgrade Mattermost to version 9.11.7 or later for 9.x branches, or version 10.4.2 or later for 10.x branches to ensure sessions are properly invalidated during user-to-bot conversion.

Recommended fix High confidence

Upgrade to Mattermost Server 9.11.7 (if on 9.11.x) or 10.4.2 (if on 10.4.x)

  1. 1. Back up your Mattermost database and configuration files before upgrading.
  2. 2. Review the Mattermost Upgrade Guide at https://docs.mattermost.com/upgrade/upgrade-mattermost.html for your deployment method.
  3. 3. If using Mattermost Omnibus or a package manager, update to the latest package: for RHEL/CentOS use 'sudo yum update mattermost-server' or for Ubuntu/Debian use 'sudo apt update && sudo apt install mattermost-server'.
  4. 4. If using a manual installation, download the target version (9.11.7 or 10.4.2) from https://mattermost.com/download/, stop the Mattermost service, replace the binary, and restart the service.
  5. 5. After upgrade, verify that all active sessions were invalidated for users converted to bots by having users log in again.
  6. 6. Test that bot functionality works correctly with the new session tokens.
  7. 7. Verify the Mattermost server starts without errors in the logs.
Caveat Review the Changelog for version 9.11.7 and 10.4.2 for any breaking changes or deprecations specific to your configuration, particularly around bot permissions and session handling.

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
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,088.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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