CVE-2023-7113
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 version 8.1.6 and earlier fails to sanitize channel mention data in posts, which allows an attacker to inject markup in the web client.
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 confidenceMattermost versions 8.1.6 and earlier contain a stored cross-site scripting (XSS) vulnerability where channel mention data in posts is not properly sanitized before rendering in the web client, allowing attackers to inject arbitrary HTML/JavaScript markup.
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< 8.1.7CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Mattermost Server versionAccess the Mattermost System Console by logging in as an admin, then navigate to 'About' page (usually at /about) or run 'mattermost version' from the server command line if you have shell accessAffected if The installed version is anything below 8.1.7 (for example, 8.1.6, 8.1.5, 8.1.0, etc.)
-
Confirm web client is in useVerify that users access Mattermost through the web browser interface at your deployment URLAffected if The web client is enabled and users browse to Mattermost via a web browser - this is the attack surface for the XSS
-
Check for channel mention functionalityReview posts in your Mattermost instance to see if channel mentions (@channel, @all, @here, or custom channel mentions) are used by users in regular communicationAffected if Channel mentions are actively used in posts within your Mattermost instance, as this is the data that is not properly sanitized
You are affected if your Mattermost Server version is below 8.1.7 and users access the web client and use channel mentions in posts.
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 · scoped8.1.7
Upgrade Mattermost to version 8.1.7 or later which includes proper sanitization of channel mention data.
Mattermost Server 8.1.7 or later
- 1. Back up your Mattermost Server database and configuration files
- 2. Download Mattermost Server version 8.1.7 or later from the official Mattermost download page
- 3. Review the Mattermost upgrade guide for your specific deployment type
- 4. Stop the Mattermost Server service
- 5. Install the upgraded Mattermost Server package
- 6. Verify the upgrade was successful by checking the server version in the system console
- 7. Test that the channel mention functionality works correctly and that XSS payloads are properly sanitized
- 8. Restart the Mattermost Server service
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-7113 — 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-7113 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