CVE-2023-4107
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 requesting user permissions when updating a system admin, allowing a user manager to update a system admin's details such as email, first name and last name.
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 validate user permissions when updating system administrator accounts. A user with the user manager role can modify sensitive details of a system admin account (email, first name, last name) due to insufficient authorization checks, allowing privilege escalation.
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.8.0, < 7.8.8>= 7.9.0, < 7.9.6>= 7.10.0, < 7.10.4CVSS 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
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/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 the installed Mattermost versionRun 'mattermost version' from the Mattermost server command line, or check the System Console > About page for the exact version numberAffected if The version falls within >= 7.8.0 and < 7.8.8, OR >= 7.9.0 and < 7.9.6, OR >= 7.10.0 and < 7.10.4
-
Determine if user manager roles are assignedNavigate to System Console > Users, or use the mmctl command 'mmctl user list --roles' to identify users granted the 'user_manager' roleAffected if Any user account is assigned the user_manager role in the system
-
Verify system administrator accounts existCheck System Console > Users and identify accounts with system_admin role, noting their email addresses and profile detailsAffected if There are one or more system administrator accounts in the deployment
-
Confirm user manager can access admin account settingsLog in with a user assigned the user_manager role and attempt to view or edit a system admin user's profile (email, first name, last name fields) in System Console > UsersAffected if The user_manager role can modify sensitive fields on system admin accounts without receiving an authorization error
Your environment is affected if you run an affected Mattermost version AND have users with the user_manager role in a system that contains administrator accounts.
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.87.9.67.10.4
Apply the vendor patch that corrects the permission validation logic to ensure only users with appropriate system admin privileges can modify system administrator account details.
Upgrade to Mattermost 7.8.8, 7.9.6, or 7.10.4 (preferably 7.10.4 for the latest stable release with all fixes)
- 1. Back up your Mattermost database and configuration files before proceeding with the upgrade
- 2. Download the appropriate Mattermost fixed version (7.8.8, 7.9.6, or 7.10.4) from the official Mattermost download page
- 3. Stop the Mattermost server to prevent active connections during the upgrade
- 4. Replace the existing Mattermost installation with the new version files
- 5. Restart the Mattermost server
- 6. Verify the upgrade was successful by checking the system console shows the new version number
- 7. Test that user management authorization controls are working correctly by attempting to update a system admin user (as a user manager, this should now be denied)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-4107 — 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-4107 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