CVE-2017-18889 — mattermost-server
MEDIUMCVE-2017-18889 is a medium-severity (CVSS 4.3) Improper Input Validation vulnerability in github.com/mattermost/mattermost-server. A fix is available for github.com/mattermost/mattermost-server — see the affected versions and patch details below.
Mattermost Server is vulnerable to webhook and slash command manipulation
EPSS Exploitation Probability
Probability of exploitation in the next 30 days, from FIRST.org EPSS.
How urgent is this, really
Where this sits among everything scored
Real-World Exposure
github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-server🐹github.com/mattermost/mattermost-serverReal-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.
Description
An issue was discovered in Mattermost Server before 4.3.0, 4.2.1, and 4.1.2. An attacker could create fictive system-message posts via webhooks and slash commands, in the v3 or v4 REST API.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-server | all versions | 4.1.2go get github.com/mattermost/mattermost-server@v4.1.2 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.2.0-rc1&&< 4.2.1 | 4.2.1go get github.com/mattermost/mattermost-server@v4.2.1 |
| 🐹Go | github.com/mattermost/mattermost-server | ≥ 4.3.0-rc1&&< 4.3.0 | 4.3.0go get github.com/mattermost/mattermost-server@v4.3.0 |
Affected Products
mattermost servermattermostDetection & mitigation playbook
Open-source dependencyDetect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/mattermost/mattermost-server, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-server to 4.1.2 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2017-18889 is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
Frequently Asked Questions
Is CVE-2017-18889 in your dependencies?
Find it across Go, including transitive dependencies.