CVE-2023-3591
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 invalidate previously generated password reset tokens when a new reset token was created.
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 confidenceIn Mattermost, when a user requests a new password reset token, any previously generated tokens for that user remain valid. An attacker with access to an old token (via email interception, log exposure, or other means) can still use it to reset the user's password even after a newer token was requested.
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.7>= 7.9.0, < 7.9.5>= 7.10.0, < 7.10.3CVSS 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
- High
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/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 'mmctl version' or check the Mattermost System Console > About page to find the exact version number installedAffected if Installed version falls within 7.8.0-7.8.6, 7.9.0-7.9.4, or 7.10.0-7.10.2
-
Review password reset token logsSearch Mattermost logs for 'password reset' or 'token' events using grep or the search functionality in the admin consoleAffected if Multiple password reset tokens exist for the same user or old tokens appear in logs
-
Audit recent password reset activityCheck the Mattermost audit logs for password reset events, looking for multiple reset requests per user accountAffected if A user shows more than one password reset token generation without corresponding successful password changes
-
Inspect password reset token storageQuery the database (Tokens table) to see if multiple active reset tokens exist for individual usersAffected if More than one active password reset token is stored for any user account
You are affected if your Mattermost Server version is 7.8.0-7.8.6, 7.9.0-7.9.4, or 7.10.0-7.10.2 AND you have any users who have requested password resets multiple times.
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.77.9.57.10.3
Apply the vendor patch to ensure previously generated password reset tokens are invalidated when a new reset token is created. Until patched, monitor for unauthorized password reset attempts.
Mattermost Server 7.10.3 (or later stable release)
- Back up the Mattermost database and configuration files before proceeding with the upgrade
- Stop the Mattermost server service
- Upgrade Mattermost Server to version 7.8.7, 7.9.5, or 7.10.3 (or later)
- Verify the upgrade was successful by checking the server version
- Start the Mattermost server service
- Verify that password reset functionality works correctly and that old tokens are now invalidated when new ones are requested
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-3591 — 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-3591 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