Mattermost Jira Plugin vulnerable to Cross-Site Request ForgeryGHSA-4fp6-574p-fc35
LOWFix: mattermost/mattermost-plugin-jira@f4cf4c6GHSA-4fp6-574p-fc35 is a low-severity (CVSS 3.5) Cross-Site Request Forgery (CSRF) vulnerability in github.com/mattermost/mattermost-plugin-jira. A fix is available for github.com/mattermost/mattermost-plugin-jira — see the affected versions and patch details below.
Exploitation Status
No confirmed exploitation observed yet
- CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.
Exploitation and automatability from CISA’s SSVC triage for GHSA-4fp6-574p-fc35.
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-plugin-jiraReal-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
Mattermost Jira Plugin fails to protect against logout CSRF allowing an attacker to post a specially crafted message that would disconnect a user's Jira connection in Mattermost only by viewing the message.
Affected Packages
| Ecosystem | Package | Vulnerable range | Fix |
|---|---|---|---|
| 🐹Go | github.com/mattermost/mattermost-plugin-jira | all versions | 1.1.2-0.20230830170046-f4cf4c6de017go get github.com/mattermost/mattermost-plugin-jira@v1.1.2-0.20230830170046-f4cf4c6de017 |
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-plugin-jira, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update github.com/mattermost/mattermost-plugin-jira to 1.1.2-0.20230830170046-f4cf4c6de017 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-4fp6-574p-fc35 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 GHSA-4fp6-574p-fc35 in your dependencies?
Find it across Go, including transitive dependencies.