CVE-2023-2784
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 verify if the requestor is a sysadmin or not, before allowing `install` requests to the Apps allowing a regular user send install requests to the Apps.
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 does not perform authorization checks to verify that a requestor has sysadmin privileges before processing App 'install' requests, allowing authenticated regular users to install Apps that should require administrator permissions.
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.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
- 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.
-
Determine Mattermost server versionAccess the System Console > About page, or query the API endpoint /api/v4/system/about, or check the package/version info in your deploymentAffected if The installed version falls within >= 7.8.0 and <= 7.8.4, >= 7.9.0 and <= 7.9.3, or equals 7.10.0
-
Verify Apps framework is enabledNavigate to System Console > Plugins > Apps Framework, or check the Apps settings in config.json, or query the plugins API endpointAffected if The Apps Framework plugin is enabled and running on the server
-
Confirm Apps plugin permissions for non-admin usersNavigate to System Console > Permissions > Roles, or use the API to list role permissions, or attempt to access the Apps marketplace as a non-sysadmin userAffected if Non-sysadmin authenticated users have permission to access or install Apps through the Apps Framework
You are affected if your Mattermost version is 7.8.0 through 7.8.4, 7.9.0 through 7.9.3, or 7.10.0 AND the Apps Framework plugin is enabled AND regular users can access App install functionality without sysadmin privileges.
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 · scopedImplement server-side authorization validation to confirm the requesting user has sysadmin role before processing any App install operations.
Upgrade to Mattermost 7.8.5+, 7.9.4+, or 7.10.1+ (or latest stable version)
- 1. Identify the current Mattermost version in use by checking the system console or running `mattermost version`
- 2. For Mattermost 7.8.x users: Upgrade to version 7.8.5 or later
- 3. For Mattermost 7.9.x users: Upgrade to version 7.9.4 or later
- 4. For Mattermost 7.10.0 users: Upgrade to version 7.10.1 or later
- 5. After upgrade, verify the fix by ensuring only sysadmins can install Apps in the system console
- 6. Review installed Apps to ensure no unauthorized Apps were installed during the vulnerable period
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing5.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,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-2784 — 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-2784 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