# CVE-2024-24774: Missing authorization allows users to access arbitrary security levels on Jira through webhooks (Jira Plugin)

> Registered Jira users can access all issues via webhooks due to missing security level checks in the Mattermost Jira Plugin.

- **Severity:** Low 3.4 (`CVSS:3.1/AV:N/AC:L/PR:H/UI:R/S:C/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 9 Feb 2024
- **Updated:** 21 Aug 2024
- **Also known as:** BIT-mattermost-2024-24774, GHSA-qr8f-cjw7-838m, GO-2024-2540

## What is CVE-2024-24774?

CVE-2024-24774 is a low-severity missing authorization vulnerability in Mattermost Mattermost Server, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.

### Official description

Mattermost Jira Plugin handling subscriptions fails to check the security level of an incoming issue or limit it based on the user who created the subscription resulting in registered users on Jira being able to create webhooks that give them access to all Jira issues.

Weakness: CWE-863 (Incorrect Authorization)

## Which versions are affected by CVE-2024-24774?

4 open source packages ship an affected version, including github.com/mattermost/mattermost-plugin-jira and mattermost. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | None |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | 4.0.0-rc1 |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | 4.0.0-rc1 |
| `mattermost` | Bitnami | All versions | 9.6.1 |

Products: Mattermost Mattermost Server.

## How do I fix CVE-2024-24774?

Upgrade github.com/mattermost/mattermost-plugin-jira to 4.0.0-rc1 or later.

## Is CVE-2024-24774 being exploited?

There is no known exploitation of CVE-2024-24774 in the wild and no public exploit code.

## Other vulnerabilities in Mattermost Mattermost Server

- [CVE-2025-12419](https://insights.sbomify.com/CVE-2025-12419/): Account takeover on OAuth/OpenID-enabled servers (critical 9.9)
- [CVE-2025-12421](https://insights.sbomify.com/CVE-2025-12421/): Account Takeover via Code Exchange Endpoint (critical 9.9)
- [CVE-2025-4981](https://insights.sbomify.com/CVE-2025-4981/): Path Traversal Leading to RCE by Any Authenticated Mattermost User (critical 9.9)
- [CVE-2025-20051](https://insights.sbomify.com/CVE-2025-20051/): Arbitrary file read via block duplication in Mattermost Boards (critical 9.9)
- [CVE-2025-25279](https://insights.sbomify.com/CVE-2025-25279/): Arbitrary file read in Mattermost Boards via import & export board archive (critical 9.9)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2024-24774 and fix it if it is affected.

What it is: CVE-2024-24774 is a low-severity missing authorization vulnerability in Mattermost Mattermost Server, published on 9 Feb 2024. An attacker needs administrator access to exploit it, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2024-24774 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mattermost/mattermost-plugin-jira (Go): affected all versions; no fix listed
- github.com/mattermost/mattermost-plugin-jira (Go): affected all versions; fixed in 4.0.0-rc1
- github.com/mattermost/mattermost-plugin-jira (Go): affected all versions; fixed in 4.0.0-rc1
- mattermost (Bitnami): affected all versions; fixed in 9.6.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2024-24774/ (Markdown: https://insights.sbomify.com/CVE-2024-24774/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2024-24774
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2024-24774
- OSV: https://osv.dev/vulnerability/CVE-2024-24774

---
From sbomify Insights: https://insights.sbomify.com/CVE-2024-24774/
Summaries are generated and may contain mistakes; the official description above is the record.