CVE-2023-5195
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 properly validate the permissions when soft deleting a team allowing a team member to soft delete other teams that they are not part of
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 lacks proper authorization checks in the soft delete team functionality, allowing authenticated team members to delete teams they are not members of. This is a broken access control vulnerability where the permission validation is missing or insufficient in the team deletion API endpoint.
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.0.0, < 7.8.10>= 8.0.0, < 8.0.2>= 8.1.0, < 8.1.1CVSS 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
- None
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Mattermost versionCheck the Mattermost server version by logging into the system and navigating to the System Console > About, or by running the command: `mattermost version` or checking the /api/v4/system/info endpointAffected if The version falls within >= 7.0.0, < 7.8.10 OR >= 8.0.0, < 8.0.2 OR >= 8.1.0, < 8.1.1
-
Confirm team API endpoints are accessibleVerify that the Mattermost API is exposed and that user authentication is enabled. Check that API requests can be made using valid user credentialsAffected if API endpoints are accessible and user authentication is functional
-
Verify soft delete team functionality existsConfirm the Mattermost instance has team management features enabled. Check that teams can be managed through the system by users with appropriate accessAffected if Teams functionality is present and the soft delete endpoint (typically /api/v4/teams/{team_id}) exists in the API
A user is affected if their Mattermost installation version is within the affected ranges AND the team management API is accessible to authenticated users, since the vulnerability allows any authenticated user to soft delete teams they are not members of.
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 · scoped7.8.108.0.28.1.1
Apply the vendor patch that adds proper permission validation to ensure users can only soft delete teams they have appropriate permissions for.
7.8.10, 8.0.2, or 8.1.1 (or later stable release)
- 1. Backup your Mattermost instance and database before upgrading.
- 2. Download the fixed version of Mattermost (7.8.10, 8.0.2, or 8.1.1) from the official Mattermost download page.
- 3. Follow the official Mattermost upgrade documentation for your deployment method (e.g., Ansible, Docker, Helm, or manual upgrade).
- 4. After upgrade, verify that the Mattermost server starts successfully.
- 5. Test that team deletion permissions now properly restrict users to only delete teams they are members of.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-5195 — 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-5195 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