CVE-2016-11074
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 3.0.0. A password-reset link could be reused.
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 confidenceMattermost Server before version 3.0.0 contains a vulnerability where password reset tokens are not invalidated after single use, allowing an attacker who intercepts or obtains a valid password reset link to reuse it multiple times for unauthorized account access.
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< 3.0.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/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 versionLocate and read the version information for your Mattermost Server installation (typically available via the system status page, configuration file, or the Mattermost command line tool)Affected if The installed version is below 3.0.0
-
Confirm version comparisonCompare your identified version number against the 3.0.0 threshold provided in the affected version rangeAffected if Your version is less than 3.0.0 (for example, 2.x.x series)
-
Verify password reset is enabledCheck whether the password reset feature is active in your Mattermost configuration (typically found in config.json or system console settings)Affected if Password reset functionality is enabled and users can request password reset links
-
Audit password reset token usageReview your Mattermost server logs for repeated password reset attempts using the same token, which would indicate exploitation of this vulnerabilityAffected if Multiple password resets are observed using identical reset tokens
You are affected if your Mattermost Server version is below 3.0.0 and password reset functionality is enabled.
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 · scoped3.0.0
Upgrade to Mattermost Server 3.0.0 or later which implements proper token invalidation after single use. If upgrade is not immediately feasible, consider implementing additional logging/monitoring for repeated password reset attempts.
Mattermost Server 3.0.0 or later
- 1. Backup your Mattermost database and configuration files before upgrading
- 2. Check your current Mattermost Server version (usually in System Console > About)
- 3. Download Mattermost Server 3.0.0 or a later stable release from https://mattermost.com/download/
- 4. Follow the official upgrade instructions for your deployment method (e.g., Docker, Ubuntu, RHEL/CentOS)
- 5. After upgrade, verify the password reset functionality works correctly with single-use links
- 6. Test that previously used password reset links are now rejected
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-11074 — 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-2016-11074 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