CVE-2016-11079
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. It allows XSS via a redirect URL.
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 Cross-Site Scripting (XSS) vulnerability in its redirect URL handling. The application fails to properly sanitize or encode redirect URL parameters, allowing attackers to inject malicious JavaScript that executes in the context of a victim's browser when they interact with a crafted redirect link.
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
- Required
- Scope
- Changed
- Confidentiality
- Low
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/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.
-
Determine installed Mattermost Server versionAccess the Mattermost System Console via the web UI, navigate to About > Mattermost, or query the API endpoint /api/v1/system/status to retrieve the server version stringAffected if The reported version is lower than 3.0.0 (for example, 2.x.x, 1.x.x)
-
Locate Mattermost configuration fileIdentify the mattermost.cfg or config.json file in the Mattermost installation directory (commonly under /opt/mattermost or the application root)Affected if The configuration file exists and contains redirect-related settings (such as SiteURL, LandingPage, or custom redirect parameters)
-
Inspect redirect URL parameters in useReview web server logs or proxy access logs for incoming requests to Mattermost that contain redirect= or next= query parametersAffected if Redirect parameters are being processed by the server without visible sanitization in the logs or application behavior
-
Verify web application behavior with crafted redirect URLIf permitted in a non-production environment, attempt to access a known Mattermost page with a redirect parameter set to a test value (such as redirect=javascript:alert(1)) and observe whether the value is reflected in the responseAffected if The test redirect value is reflected in the HTML response without encoding or is used in a Location header
A user is affected if their Mattermost Server installation is version 2.x.x or lower and the server processes redirect URL parameters that are not sanitized before use.
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 data3.0.0
Upgrade Mattermost Server to version 3.0.0 or later. If immediate upgrading is not feasible, implement proper input validation and output encoding on all redirect URL parameters to neutralize script injection attempts.
- 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-2016-11079 — 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-11079 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