dbcve.org
Mattermost DesktopApplication · Mattermost

CVE-2023-5875

MEDIUM · 5.3 CVSS v3.1 Published 2023-11-02
Fix available
A fix is available. Upgrade to 5.5.1 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 Desktop fails to correctly handle permissions or prompt the user for consent on certain sensitive ones allowing media exploitation from a malicious 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 · moderate confidence

Mattermost Desktop application fails to properly handle sensitive permission requests, not prompting users for consent before granting access. A malicious Mattermost server can exploit this to access media resources (likely camera, microphone, or screen sharing) without user awareness.

MitigationUsers should update to the patched version of Mattermost Desktop. Organizations should verify their Mattermost Desktop client versions and apply updates. Until patched, users should be cautious about granting any permission requests and verify the server they are connecting to is trusted.

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 DesktopApplication
Affected:< 5.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
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. Check installed Mattermost Desktop version
    Open the Mattermost Desktop app, then go to Help > About Mattermost (Windows/Linux) or click the app name in the menu bar > About Mattermost (Mac). Alternatively, right-click the Mattermost Desktop executable file and view its Properties > Details to see the Product Version.
    Affected if The displayed version is less than 5.5.1 (for example, 5.5.0, 5.4.x, or earlier)
  2. Verify the version via system package manager
    On Windows, run 'Get-ItemProperty -Path "C:\Program Files\Mattermost\Mattermost Desktop\Mattermost Desktop.exe" | Select-Object VersionInfo' in PowerShell. On macOS, run 'defaults read /Applications/Mattermost\ Desktop.app/Contents/Info CFBundleShortVersionString' in Terminal.
    Affected if The returned version number is below 5.5.1
  3. Confirm active server connection
    Open Mattermost Desktop and verify which Mattermost server(s) the client is connected to by checking the server URL in the bottom-left corner or in the server list. This vulnerability is exploitable only when connecting to a malicious or untrusted Mattermost server.
    Affected if The client is connected to any server (the vulnerability allows a malicious server to bypass permission prompts, so any connection to an untrusted server could trigger the issue)

You are affected if your Mattermost Desktop version is below 5.5.1 and you connect to a Mattermost server, as the client will not prompt for consent before granting media access permissions.

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 5.5.1 or later
Fixed in 5.5.1
Interim mitigation

Users should update to the patched version of Mattermost Desktop. Organizations should verify their Mattermost Desktop client versions and apply updates. Until patched, users should be cautious about granting any permission requests and verify the server they are connecting to is trusted.

Recommended fix Moderate confidence

5.5.1 or later

  1. Check the current Mattermost Desktop version by clicking Help > About Mattermost
  2. If the installed version is earlier than 5.5.1, download the latest Mattermost Desktop client from the official Mattermost website (mattermost.com) or your organization's software distribution channel
  3. Install the updated Mattermost Desktop application using standard installation procedures
  4. Restart the application if prompted or manually restart to ensure the update is fully applied

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

Fix this in Mattermost Desktop Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA3.0 h
19.0 hours of engineering $3,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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