CVE-2023-46701
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 perform authorization checks in the /plugins/playbooks/api/v0/runs/add-to-timeline-dialog endpoint of the Playbooks plugin allowing an attacker to get limited information about a post if they know the post ID
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 confidenceThe Playbooks plugin's /plugins/playbooks/api/v0/runs/add-to-timeline-dialog endpoint fails to validate user authorization before returning post information, allowing any authenticated user to query limited details about posts by knowing the post ID (an Insecure Direct Object Reference vulnerability).
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.14>= 8.0.0, <= 8.1.5>= 9.0.0, <= 9.0.3>= 9.1.1, <= 9.1.2>= 9.2.0, <= 9.2.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/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.
-
Check Mattermost Server versionRun `grep -i version /opt/mattermost/version.txt` or access the server diagnostics at /api/v4/system/stats or check the About section in the System ConsoleAffected if The installed version falls within <= 7.8.14, >= 8.0.0 through <= 8.1.5, >= 9.0.0 through <= 9.0.3, >= 9.1.1 through <= 9.1.2, or >= 9.2.0 through <= 9.2.1
-
Verify Playbooks plugin is enabledNavigate to System Console > Plugins > Plugin Management and confirm the 'Playbooks' plugin status, or query the API at /api/v4/plugins with admin credentialsAffected if The Playbooks plugin is installed and enabled
-
Confirm API endpoint existsSend an authenticated GET request to /plugins/playbooks/api/v0/runs/add-to-timeline-dialog with a valid post ID parameterAffected if The endpoint responds with post details without verifying the user has permission to access that post (returns 200 OK with post information rather than 403 Forbidden)
A user is affected if they run a vulnerable Mattermost Server version (within the ranges listed) AND have the Playbooks plugin enabled, allowing any authenticated user to query post details via the vulnerable endpoint without authorization checks.
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 the vendor patch for CVE-2023-46701 which adds proper authorization checks to verify the requesting user has permission to access the post before returning information.
Upgrade to the latest version of Mattermost Server (recommended: 7.8.15, 8.1.6, 9.0.4, or 9.1.3 or later depending on your current major version)
- 1. Identify the current Mattermost Server version by navigating to System Console > About or checking the Mattermost logs
- 2. If running version <= 7.8.14, upgrade to version 7.8.15 or later
- 3. If running version >= 8.0.0 and <= 8.1.5, upgrade to version 8.1.6 or later
- 4. If running version >= 9.0.0 and <= 9.0.3, upgrade to version 9.0.4 or later
- 5. If running version >= 9.1.1 and <= 9.1.2, upgrade to version 9.1.3 or later
- 6. After upgrading, verify the Playbooks plugin is updated to a compatible version
- 7. Test the /plugins/playbooks/api/v0/runs/add-to-timeline-dialog endpoint to confirm authorization is now properly enforced
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation3.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,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-46701 — 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-46701 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