dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-25068

HIGH · 8.8 CVSS v3.1 Published 2025-03-21
Fix available
A fix is available. Upgrade to 9.11.9 / 10.3.4 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 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, 9.11.x <= 9.11.8, 10.5.x <= 10.5.0 fail to enforce MFA on plugin endpoints, which allows authenticated attackers to bypass MFA protections via API requests to plugin-specific routes.

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 enforce MFA on plugin endpoints in versions 10.4.x <= 10.4.2, 10.3.x <= 10.3.3, 9.11.x <= 9.11.8, and 10.5.x <= 10.5.0, allowing authenticated attackers to bypass MFA protections by making API requests directly to plugin-specific routes.

MitigationEnable and enforce MFA for all users, and review plugin configurations to ensure plugin endpoints properly enforce MFA authentication. Consider updating to a patched version once available.

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.9>= 10.3.0, < 10.3.4>= 10.4.0, < 10.4.3>= 10.5.0, < 10.5.1

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 Mattermost Server version
    Run 'sudo mattermost version' or check the version through the System Console under About > Mattermost, or inspect the /opt/mattermost/version file
    Affected if The installed version falls within 9.11.0-9.11.8, 10.3.0-10.3.3, 10.4.0-10.4.2, or 10.5.0-10.5.0
  2. Identify enabled plugins
    Navigate to System Console > Plugins > Management, or use the Mattermost CLI: 'mattermost plugin list'
    Affected if Any third-party or custom plugins are installed and enabled, as the vulnerability affects plugin endpoint MFA enforcement
  3. Verify if MFA is configured
    Check System Console > Authentication > MFA, or inspect the SiteURL and authentication settings via the Mattermost API endpoint /api/v4/config
    Affected if MFA is not enabled or not enforced for user accounts, making the bypass possible
  4. Check for plugin API endpoints
    Review installed plugin manifests and documentation to identify which plugins expose API routes, or examine the plugin API paths under /plugins/*/api/*
    Affected if Plugins with exposed API routes are active, as these routes can bypass MFA validation

You are affected if your Mattermost Server version is 9.11.0-9.11.8, 10.3.0-10.3.3, 10.4.0-10.4.2, or 10.5.0-10.5.0 AND you have plugins with API endpoints enabled AND MFA is not enforced.

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.9 / 10.3.4 / 10.4.3 or later
Fixed in 9.11.910.3.410.4.3
Interim mitigation

Enable and enforce MFA for all users, and review plugin configurations to ensure plugin endpoints properly enforce MFA authentication. Consider updating to a patched version once available.

Recommended fix High confidence

Upgrade to 9.11.9 (for 9.11.x), 10.3.4 (for 10.3.x), 10.4.3 (for 10.4.x), or 10.5.1 (for 10.5.x) depending on your current version branch

  1. 1. Identify your current Mattermost Server version by navigating to System Console > About or checking the mattermost version command
  2. 2. If running 9.11.x (9.11.0 through 9.11.8), upgrade to Mattermost Server 9.11.9 or later
  3. 3. If running 10.3.x (10.3.0 through 10.3.3), upgrade to Mattermost Server 10.3.4 or later
  4. 4. If running 10.4.x (10.4.0 through 10.4.2), upgrade to Mattermost Server 10.4.3 or later
  5. 5. If running 10.5.0 through 10.5.0, upgrade to Mattermost Server 10.5.1 or later
  6. 6. After upgrade, verify MFA enforcement on plugin endpoints is functioning correctly
  7. 7. Review Mattermost upgrade documentation for any pre-upgrade steps or migration requirements
Caveat Review Mattermost upgrade guides for version-specific breaking changes and ensure backup before upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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