CVE-2024-23319: CSRF issue allows disconnecting a user's Jira connection through a simple post message (Jira Plugin)
Noroxi assessment
Priority: Monitor (action score 14/100)
- The sources we track (CISA KEV, Exploit-DB, Metasploit, Nuclei, GitHub) show no public exploit code or exploitation in the wild.
- Probability of exploitation in the next 30 days: 0.24% (FIRST EPSS).
- Anyone who can reach it over the internet can trigger it. A low-privileged account is enough. A user must open a link or visit a page. No special conditions are required; it is repeatable.
- Fixed version: github.com/mattermost/mattermost-plugin-jira (Go) 1.1.2-0.20230830170046-f4cf4c6de017.
Low priority for now. Upgrade to github.com/mattermost/mattermost-plugin-jira (Go) 1.1.2-0.20230830170046-f4cf4c6de017 or later.
Generated automatically from the record's data: CVSS (NVD and CNA), CISA KEV and SSVC, FIRST EPSS, exploit sources, fixed versions. How we calculate it
Primary sources: NVD · CVE.org · FIRST EPSS
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.
- Published
- Feb 9, 2024
- Updated
- Jun 17, 2026
- EPSS
- 0.2% · 15th percentile
- CWE
- CWE-352
Report tools
Action score
14
Monitor
Low priority for now.
- CVSS
- 14 / 40 · 3.5 / 10
- CISA KEV
- 0 / 30 · Not listed
- EPSS
- 0 / 30 · 0.2%
CISA SSVC decision
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
Vulnrichment: CISA's decision-tree inputs.
CNA vs NVD score
- NVD
- 3.5
- CNA · Mattermost
- 3.5
- agree
The score given by the assigning authority versus NVD’s independent score. A gap means the severity is contested.
Get told when this record changes
- Not in KEV: no record of exploitation in the wild
- No public exploit code on record
- A fix has been released
If any of these changes, we'll tell you in the daily email digest.
Running WordPress? Scan your site free with WP Lens
Noroxi analysis
What does it mean in your environment?
The assessment above is generated automatically from the record's data; it doesn't know your environment. Our team verifies on your systems whether this vulnerability is actually exploitable and which mitigation is enough.
We use this product, ask for helpAffected systems
Is your version affected?
Pick the product and type the version you run. It's compared with this record's version ranges in your browser; the version isn't sent anywhere.
| Vendor | Product | CPE |
|---|---|---|
| mattermost | mattermost server | cpe:2.3:a:mattermost:mattermost_server |
Affected versions
NVD version ranges (for catalog products). Add the product to your stack with a version and matching uses these.
- mattermost mattermost serverup to 8.1.7 inclusive
Versions reported by the vendor
Affected version ranges reported by the assigning authority (Mattermost). Independent of NVD's CPE analysis and usually ahead of it.
Mattermost Mattermost
- 8.1.8not affected
- up to and including 8.1.7affected · semver
Package-level exposure
OSV and GitHub Advisory data: ecosystem, package and range. SBOM matching uses this table.
| Ecosystem | Package | Affected range | Fix |
|---|---|---|---|
| Go | github.com/mattermost/mattermost-plugin-jira | before 1.1.2-0.20230830170046-f4cf4c6de017 | 1.1.2-0.20230830170046-f4cf4c6de017 |
Same product
mattermost: all recordsOther highest-scoring records for the same primary product.
- CVE-2026-4858Path traversal in integration action URL leading to arbitrary API execution via system admin’s auth token.39Monitor
- CVE-2025-12421Account Takeover via Code Exchange Endpoint39Monitor
- CVE-2025-12419Account takeover on OAuth/OpenID-enabled servers39Monitor
Published before and after this one in the same product
- ← EarlierCVE-2023-48732Jan 2, 2024 · Keywords that trigger mentions are leaked to other users17Monitor
- ← EarlierCVE-2023-50333Jan 2, 2024 · Lack of restriction to manage group names for freshly demoted guests17Monitor
- Later →CVE-2024-24774Feb 9, 2024 · Missing authorization allows users to access arbitrary security levels on Jira through webhooks (Jira Plugin)16Monitor
Remediation
Which version to upgrade to
Fix versions compiled from the vendor, package registries and Microsoft. Verify the vendor's note before upgrading.
| Product / package | Fixed version | Source |
|---|---|---|
| Go:github.com/mattermost/mattermost-plugin-jira | 1.1.2-0.20230830170046-f4cf4c6de017 | Package registry (OSV) |
Exploit status
No known public exploit
No public exploit has been observed yet. That doesn't mean you're safe, only that the bar is a little higher.
Research context
For pentesters and researchers: attack profile, score disagreement, timeline, patch commits, credits, variant and chain candidates, bug bounty scope. All derived from existing data; no exploit code.
Timeline
From publication to today: proof of concept, Metasploit module, CISA KEV and fix record. Dates are as reported by the sources.
No dated events beyond publication.
No history yet (it accumulates with the daily EPSS job).
Patch and commit links
Commit, PR and diff links among the references. A starting point for patch-diffing and variant hunting; fixes, not exploits.
No commit or PR link among the references.
Credits
All researchersFinders, reporters and analysts named in the CNA record. Click a name for that researcher’s other records.
- Rohitesh Guptafinder
Variant candidates
Same product, same weakness class, within 18 months. If the patch missed the root cause, the sibling bug is here.
- CVE-2023-4531659 days apartReflected client side path traversal leading to CSRF in Playbooks35Monitor
- CVE-2024-36255107 days apartPost actions can run playbook checklist task commands22Monitor
- CVE-2024-46872263 days apartClient-Side Path Traversal Leading to CSRF in Playbooks18Monitor
Chain candidates
An authentication bypass and a privilege-requiring bug in the same product, published close together: combined they may become an unauthenticated path.
—
Bug bounty scope
The product’s vendor appears in a public program. Matched by name; verify the scope text in the program.
Technical details
Attack conditions
- Anyone who can reach it over the internet can trigger it.
- A low-privileged account is enough.
- A user must open a link or visit a page.
- No special conditions are required; it is repeatable.
If successful
- Confidentiality
- none
- Integrity
- none
- Availability
- low · the service can be disrupted
- Attack vector
- Network
- Attack complexity
- Low
- Privileges required
- Low
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality impact
- None
- Integrity impact
- None
- Availability impact
- Low
Weakness class (CWE)
CWE-352 · Cross-Site Request Forgery (CSRF)CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:U/C:N/I:N/A:L
nvd-primary
Root cause
State-changing requests rely on the session cookie the browser sends automatically; nothing verifies that the request came from the user’s own page.
The bug in code
The whole CWE-352 classA representative example of this vulnerability class. Not the vendor's source code; it shows the faulty pattern and its fix.
Vulnerable
app.use(session({ cookie: { httpOnly: true } }));
app.post("/account/address", updateAddress);Fixed
app.use(session({ cookie: { httpOnly: true, sameSite: "lax" } }));
app.post("/account/address", csrfProtection, updateAddress);Attack context
MITRE CAPEC attack patterns and ATT&CK techniques for this weakness class (CWE). A starting point for detection rules and threat hunting.
Change log
- Fix✗ → ✓
For records you follow, these changes also arrive as notifications. →
References
Vendor advisories and official records. Exploit/PoC links are deliberately left out.