CVE-2019-20876
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 · uneditedAn issue was discovered in Mattermost Server before 5.9.0, 5.8.1, 5.7.3, and 4.10.8. Users can deactivate themselves, bypassing a policy.
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 confidenceIn affected Mattermost Server versions, the system allows users to deactivate their own accounts without properly enforcing administrator-defined policies that may restrict self-deactivation. This represents a bypass of intended access control restrictions.
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< 4.10.8>= 5.7.0, < 5.7.3>= 5.8.0, < 5.8.1= 5.9.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
- 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 the installed Mattermost Server versionAccess the system console or use the Mattermost API to retrieve the server version (typically available at /api/v4/system/stats or in the system console footer)Affected if The installed version falls into any of these ranges: < 4.10.8, >= 5.7.0 and < 5.7.3, >= 5.8.0 and < 5.8.1, or exactly 5.9.0
-
Verify if administrator policies restricting self-deactivation are definedCheck the System Console under Policies or Security settings for any configured policies that should prevent users from self-deactivating their accountsAffected if Policies restricting self-deactivation exist but users can still deactivate their own accounts regardless
-
Review account deactivation logs for unauthorized self-deactivationsExamine Mattermost audit logs or the System Console logs for deactivation events, specifically looking for instances where standard users deactivated their own accountsAffected if Audit logs show users successfully deactivated their own accounts despite admin policies that should have blocked such actions
-
Confirm whether the deactivation feature is accessible to standard usersTest or verify through documentation whether standard (non-admin) users have access to account deeletion/deactivation options in their profile settingsAffected if Standard users have the ability to deactivate their own accounts through the UI or API when they should be restricted by policy
A user is affected if their Mattermost Server version is within the vulnerable ranges listed AND standard users can bypass administrator-defined self-deactivation restrictions to deactivate their own 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.
From vendor data4.10.85.7.35.8.1
Upgrade Mattermost Server to version 5.9.0, 5.8.1, 5.7.3, or 4.10.8 or later. Until upgraded, administrators should monitor account deactivation activity closely.
- 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-2019-20876 — 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-2019-20876 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