dbcve.org
Mattermost ServerApplication · Mattermost

CVE-2024-2445

MEDIUM · 6.1 CVSS v3.1 Published 2024-03-15
Fix available
A fix is available. Upgrade to 8.1.10 / 9.2.6 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 Jira plugin versions shipped with Mattermost versions 8.1.x before 8.1.10, 9.2.x before 9.2.6, 9.3.x before 9.3.2, and 9.4.x before 9.4.3 fail to escape user-controlled outputs when generating HTML pages, which allows an attacker to perform reflected cross-site scripting attacks against the users of the Mattermost server.

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 Mattermost Jira plugin versions prior to 8.1.10, 9.2.6, 9.3.2, and 9.4.3 contain a reflected cross-site scripting (XSS) vulnerability where user-controlled data is not properly escaped before being rendered in HTML pages. An attacker can craft malicious URLs or input data that, when processed by the Jira plugin and reflected back to users, executes arbitrary JavaScript in the context of the victim's browser session.

MitigationUpgrade the Mattermost Jira plugin to version 8.1.10, 9.2.6, 9.3.2, 9.4.3 or later. Alternatively, upgrade the entire Mattermost installation to a version that ships with a patched Jira plugin.

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:>= 8.1.0, < 8.1.10>= 9.2.0, < 9.2.6>= 9.3.0, < 9.3.2>= 9.4.0, < 9.4.3

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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. Identify Mattermost Server installation
    Locate the Mattermost Server installation and determine its installation method (e.g., check for mattermost binary, Docker container, or package manager installation)
    Affected if Mattermost Server is not installed or cannot be located
  2. Determine installed Mattermost Server version
    Run 'mattermost version' or check the version displayed in the Mattermost System Console under About > Mattermost, or inspect the version file in the installation directory
    Affected if The installed version falls within any of these ranges: >= 8.1.0 and < 8.1.10, >= 9.2.0 and < 9.2.6, >= 9.3.0 and < 9.3.2, or >= 9.4.0 and < 9.4.3
  3. Verify Jira plugin is installed and enabled
    Access Mattermost System Console > Plugins > Plugin Management, or inspect the plugins/jira directory in the mattermost installation, or run 'mattermost plugin list'
    Affected if The Jira plugin is installed and enabled (the vulnerability only applies when the plugin is active)
  4. Confirm plugin version matches vulnerable release
    In the Plugins > Plugin Management page, click on the Jira plugin to view its version, or examine the plugin manifest file in the plugins/jira directory
    Affected if The Jira plugin version is earlier than 8.1.10, 9.2.6, 9.3.2, or 9.4.3 (or if the plugin version cannot be determined but the Mattermost Server version is in the affected ranges)

A user is affected if they are running Mattermost Server with the Jira plugin enabled and the installed version falls within the affected version ranges, meaning arbitrary JavaScript could execute via crafted URLs or input data processed by the plugin.

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 8.1.10 / 9.2.6 / 9.3.2 or later
Fixed in 8.1.109.2.69.3.2
Interim mitigation

Upgrade the Mattermost Jira plugin to version 8.1.10, 9.2.6, 9.3.2, 9.4.3 or later. Alternatively, upgrade the entire Mattermost installation to a version that ships with a patched Jira plugin.

Recommended fix High confidence

Upgrade to the next available patch release in your major version: 8.1.10, 9.2.6, 9.3.2, or 9.4.3 (or later)

  1. 1. Identify the current Mattermost Server version by checking the System Console > About or running 'mmctl version'
  2. 2. Determine which version series you are running (8.1.x, 9.2.x, 9.3.x, or 9.4.x)
  3. 3. For 8.1.x: Upgrade to version 8.1.10 or later
  4. 4. For 9.2.x: Upgrade to version 9.2.6 or later
  5. 5. For 9.3.x: Upgrade to version 9.3.2 or later
  6. 6. For 9.4.x: Upgrade to version 9.4.3 or later
  7. 7. Follow standard Mattermost upgrade procedures: backup database, stop server, install new version, verify startup
  8. 8. After upgrade, verify the Jira plugin is updated to the bundled version with the fix
Caveat Minor/patch upgrades typically have no breaking changes; always review release notes for any behavior changes before upgrading

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

Fix this in Mattermost Server Scoped from the published advisory
  • Consultation4.0 h
  • Implementation3.0 h
  • Testing6.0 h
  • Review / QA3.0 h
16.0 hours of engineering $2,780
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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