dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2025-14273

HIGH · 8.3 CVSS v3.1 Published 2025-12-22
Fix available
A fix is available. Upgrade to 10.11.8 / 10.12.4 or later.
See remediation →
92/100
Remediation priority · Urgent
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 11.1.x <= 11.1.0, 11.0.x <= 11.0.5, 10.12.x <= 10.12.3, 10.11.x <= 10.11.7 with the Jira plugin enabled and Mattermost Jira plugin versions <=4.4.0 fail to enforce authentication and issue-key path restrictions in the Jira plugin, which allows an unauthenticated attacker who knows a valid user ID to issue authenticated GET and POST requests to the Jira server via crafted plugin payloads that spoof the user ID and inject arbitrary issue key paths. Mattermost Advisory ID: MMSA-2025-00555

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

The Jira plugin in Mattermost fails to enforce authentication and issue-key path restrictions, allowing unauthenticated attackers who know a valid user ID to spoof that user ID and inject arbitrary issue key paths in crafted plugin payloads. This enables authenticated GET and POST requests to be issued to the Jira server without proper authorization.

MitigationUpdate Mattermost beyond the affected versions (11.1.1+, 11.0.6+, 10.12.4+, 10.11.8+) and Jira plugin beyond version 4.4.0, or disable the Jira plugin if not required.

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.11.0, < 10.11.8>= 10.12.0, < 10.12.4>= 11.0.0, < 11.0.6>= 11.1.0, < 11.1.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
None
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:L/I:L/A:L

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 if Jira plugin is installed and enabled
    Navigate to Mattermost System Console > Plugins > Plugin Management, or use the CLI command: `mattermost plugin list`. Verify the Jira plugin appears in the list and is enabled.
    Affected if The Jira plugin is present and enabled; if the plugin is not installed the vulnerability does not apply.
  2. Check Mattermost Server version
    Run `mattermost version` or check System Console > About. Compare the version number against the affected ranges: 10.11.0-10.11.7, 10.12.0-10.12.3, 11.0.0-11.0.5, or 11.1.0.
    Affected if The installed version falls within any of these ranges.
  3. Check Jira plugin version
    In System Console > Plugins > Plugin Management, click on the Jira plugin to view its version. Compare against version 4.4.0.
    Affected if The Jira plugin version is lower than 4.4.0.
  4. Check if Jira plugin is configured with a Jira instance
    Navigate to Plugins > Jira > Instance Settings, or check the plugin configuration for any connected Jira instances. A configured connection is required for the vulnerability to be exploitable.
    Affected if The Jira plugin has an active Jira instance configured and connected.

You are affected if the Jira plugin is enabled, the Mattermost Server version OR Jira plugin version falls within the affected ranges, and the Jira plugin has a configured Jira instance connection.

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.11.8 / 10.12.4 / 11.0.6 or later
Fixed in 10.11.810.12.411.0.6
Interim mitigation

Update Mattermost beyond the affected versions (11.1.1+, 11.0.6+, 10.12.4+, 10.11.8+) and Jira plugin beyond version 4.4.0, or disable the Jira plugin if not required.

Recommended fix High confidence

Upgrade to Mattermost Server 10.11.8 / 10.12.4 / 11.0.6 / 11.1.1 or later (choose the appropriate version for your current major branch, or upgrade to the latest stable release)

  1. 1. Back up your Mattermost Server data and configuration files before proceeding with any upgrade.
  2. 2. Identify your current Mattermost Server version by checking the System Console > About page.
  3. 3. For Mattermost 10.11.x: Upgrade to version 10.11.8 or later.
  4. 4. For Mattermost 10.12.x: Upgrade to version 10.12.4 or later.
  5. 5. For Mattermost 11.0.x: Upgrade to version 11.0.6 or later.
  6. 6. For Mattermost 11.1.x: Upgrade to version 11.1.1 or later.
  7. 7. After upgrading, verify the Jira plugin is updated and functioning correctly.
  8. 8. Test the Jira integration to ensure authentication and issue-key path restrictions are properly enforced.
Caveat Review release notes for your target version to check for any breaking changes or migration requirements 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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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