CVE-2023-2792
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 · uneditedMattermost fails to sanitize ephemeral error messages, allowing an attacker to obtain arbitrary message contents by a specially crafted /groupmsg command.
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 confidenceMattermost does not properly sanitize ephemeral error messages returned by the /groupmsg command. An attacker can craft a specially crafted /groupmsg command to trigger the display of arbitrary message contents through unsanitized error messages, leading to information disclosure.
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>= 7.1.0, <= 7.1.9>= 7.8.0, <= 7.8.4>= 7.9.0, <= 7.9.3= 7.10.0CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checksWork through these to decide whether this CVE applies to you.
-
Identify Mattermost server versionRun 'mattermost version' or check the System Console under About > Mattermost, or inspect the /opt/mattermost/version.txt fileAffected if The installed version falls within 7.1.0-7.1.9, 7.8.0-7.8.4, 7.9.0-7.9.3, or exactly 7.10.0
-
Confirm /groupmsg command is enabledCheck if the group message plugin or built-in /groupmsg command is available to users in the Mattermost instanceAffected if The /groupmsg feature is enabled and accessible to at least some users
-
Verify ephemeral message functionality existsConfirm the Mattermost server handles ephemeral messages (temporary messages visible only to specific users) in group messaging contextsAffected if Ephemeral messages are supported and used in group messaging scenarios
A user is affected if their Mattermost installation runs a version between 7.1.0-7.1.9, 7.8.0-7.8.4, 7.9.0-7.9.3, or exactly 7.10.0 and the /groupmsg command with ephemeral messaging is enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scopedApply output encoding and input validation to ephemeral messages in the /groupmsg command handler to ensure all displayed content is properly sanitized before rendering.
Upgrade to Mattermost 7.1.10+, 7.8.5+, 7.9.4+, or 7.10.1+ (or the latest stable 7.x/8.x release)
- Identify the currently installed Mattermost version using the system console or mmctl command
- If running 7.1.x, upgrade to version 7.1.10 or later
- If running 7.8.x, upgrade to version 7.8.5 or later
- If running 7.9.x, upgrade to version 7.9.4 or later
- If running 7.10.0, upgrade to version 7.10.1 or later
- After upgrade, verify the /groupmsg command no longer leaks information in ephemeral messages
- Review Mattermost security bulletins for any additional required patches
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2792 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-2792 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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