dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-22445

MEDIUM · 5.3 CVSS v3.1 Published 2025-01-09
Fix available
A fix is available. Upgrade to 10.3.0 or later.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges 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.x <= 10.2 fail to accurately reflect missing settings, which allows confusion for admins regarding a Calls security-sensitive configuration via incorrect UI reporting.

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 versions 10.x through 10.2 have a UI reporting issue where the admin interface fails to accurately display the status of security-sensitive configuration settings for the Calls feature. This causes administrators to believe settings are properly configured when they may actually be missing or misconfigured, leading to potential security misconfigurations.

MitigationUpgrade to a version beyond 10.2 when the patch is available. Until then, manually verify Calls security settings through direct configuration files or CLI rather than relying on the potentially inaccurate UI.

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.0.0, < 10.3.0

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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. Identify Mattermost Server version
    Run 'sudo mattermost version' or check the version file in the Mattermost installation directory (typically /opt/mattermost/version.txt)
    Affected if Version is 10.0.0 or higher but lower than 10.3.0
  2. Determine if Calls plugin is enabled
    Run 'mattermost plugin list' or check System Console > Plugin Management to see if the Calls plugin is installed and enabled
    Affected if Calls plugin is active and in use on the server
  3. Check actual Calls security configuration via CLI
    Run 'mattermost config get PluginSettings.Active' and review the PluginCalls settings in the config.json file, specifically looking for security-sensitive settings like 'Enable', 'ServerVersion', and any authentication/tls configurations
    Affected if Calls plugin is enabled and you find any security settings defined in the actual configuration file or CLI output
  4. Compare CLI configuration with UI display
    Access System Console > Plugins > Calls and visually compare the displayed security settings against what the CLI 'mattermost config get' command returns for the same settings
    Affected if The settings shown in the admin UI differ from or contradict the actual configuration values returned by the CLI or found in config.json

You are affected if running Mattermost Server 10.0.0 to less than 10.3.0, have the Calls plugin enabled, and discover a mismatch between the actual Calls security configuration and what the admin UI displays.

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.3.0 or later
Fixed in 10.3.0
Interim mitigation

Upgrade to a version beyond 10.2 when the patch is available. Until then, manually verify Calls security settings through direct configuration files or CLI rather than relying on the potentially inaccurate UI.

Recommended fix High confidence

10.3.0 or later (e.g., 10.3.0, 10.3.1)

  1. 1. Backup your Mattermost Server database and configuration files before proceeding with any upgrade
  2. 2. Review the Mattermost 10.3.0 release notes for any breaking changes or migration requirements
  3. 3. Upgrade Mattermost Server to version 10.3.0 or later (e.g., 10.3.0, 10.3.1)
  4. 4. After upgrade, verify the Calls settings page now correctly displays the security-sensitive configuration status (it should accurately reflect when settings are missing rather than showing incorrect values)
  5. 5. Confirm the admin UI properly reports the actual state of the Calls plugin configuration
Caveat Minor version upgrades in Mattermost may include breaking changes; review release notes for migration steps and compatibility notes

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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