CVE-2025-41395
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 versions 10.4.x <= 10.4.2, 10.5.x <= 10.5.0, 9.11.x <= 9.11.10 fail to properly validate the props used by the RetrospectivePost custom post type in the Playbooks plugin, which allows an attacker to create a specially crafted post with maliciously crafted props and cause a denial of service (DoS) of the web app for all users.
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 in Mattermost fails to properly validate props passed to the RetrospectivePost custom post type. Attackers can craft malicious props that cause the web application to crash, resulting in a denial of service for all users.
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>= 9.11.0, < 9.11.11>= 10.4.0, < 10.4.3>= 10.5.0, < 10.5.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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
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 versionRun `mattermost version` or `mmctl version` from the command line, or access the Mattermost System Console and navigate to About > Mattermost to view the version numberAffected if The installed version falls within >= 9.11.0 and < 9.11.11, OR >= 10.4.0 and < 10.4.3, OR >= 10.5.0 and < 10.5.1
-
Identify Playbooks plugin statusRun `mattermost plugin list` or `mmctl plugin list` to list installed plugins, or access System Console > Plugin Management to view enabled pluginsAffected if The Playbooks plugin appears in the list of enabled plugins
A user is affected if their Mattermost Server version is within the affected ranges AND the Playbooks plugin is enabled, as the vulnerability requires the Playbooks plugin to be active for the malicious props to trigger the crash.
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 · scoped9.11.1110.4.310.5.1
Upgrade Mattermost to versions beyond 10.4.2, 10.5.0, and 9.11.10 to obtain the patched releases, or temporarily disable the Playbooks plugin if immediate upgrading is not feasible.
Upgrade to 9.11.11+ (9.11.x), 10.4.3+ (10.4.x), or 10.5.1+ (10.5.x) depending on your current branch
- 1. Identify the currently installed Mattermost Server version using the system console or mmctl command
- 2. Determine which version branch you are on (9.11.x, 10.4.x, or 10.5.x)
- 3. For 9.11.x branches: upgrade to version 9.11.11 or later
- 4. For 10.4.x branches: upgrade to version 10.4.3 or later
- 5. For 10.5.x branches: upgrade to version 10.5.1 or later
- 6. After upgrade, verify the Playbooks plugin is functioning correctly
- 7. Test that the web app loads without denial of service issues
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.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 $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-41395 — 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-2025-41395 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