# CVE-2025-14273: Mattermost Jira plugin user spoofing enables Jira request forgery.

> Unauthenticated attackers can spoof user IDs to issue arbitrary Jira requests via the Mattermost Jira plugin, bypassing authentication and path restrictions.

- **Severity:** High 7.2 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:N/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 22 Dec 2025
- **Updated:** 22 Dec 2025
- **Also known as:** GHSA-qvmc-92vg-6r35, GO-2026-4275

## What is CVE-2025-14273?

CVE-2025-14273 is a high-severity missing authorization vulnerability in Mattermost Mattermost Server, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mattermost versions 11.1.x <= 11.1.0, 11.0.x <= 11.0.5, 10.12.x <= 10.12.3, 10.11.x <= 10.11.7 with the Jira plugin enabled and Mattermost Jira plugin versions <=4.4.0 fail to enforce authentication and issue-key path restrictions in the Jira plugin, which allows an unauthenticated attacker who knows a valid user ID to issue authenticated GET and POST requests to the Jira server via crafted plugin payloads that spoof the user ID and inject arbitrary issue key paths. Mattermost Advisory ID: MMSA-2025-00555

Weakness: CWE-303 (Incorrect Implementation of Authentication Algorithm)

## Which versions are affected by CVE-2025-14273?

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


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/mattermost/mattermost/server/v8` | Go | All versions | 8.0.0-20251121122154-b57c297c6d7a |
| `github.com/mattermost/mattermost/server/v8` | Go | All versions | 8.0.0-20251121122154-b57c297c6d7a |
| `github.com/mattermost/mattermost/server/v8` | Go | All versions | 8.0.0-20251121122154-b57c297c6d7a |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | None |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | 4.4.1 |
| `github.com/mattermost/mattermost-plugin-jira` | Go | All versions | 4.4.1 |
| `github.com/mattermost/mattermost-server` | Go | All versions | None |
| `github.com/mattermost/mattermost-server/v5` | Go | All versions | None |
| `github.com/mattermost/mattermost-server/v6` | Go | All versions | None |

Products: Mattermost Mattermost Server.

## How do I fix CVE-2025-14273?

Upgrade github.com/mattermost/mattermost/server/v8 to 8.0.0-20251121122154-b57c297c6d7a or later.

## Is CVE-2025-14273 being exploited?

There is no known exploitation of CVE-2025-14273 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-2025-14273 and fix it if it is affected.

What it is: CVE-2025-14273 is a high-severity missing authorization vulnerability in Mattermost Mattermost Server, published on 22 Dec 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-14273 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/mattermost/mattermost/server/v8 (Go): affected all versions; fixed in 8.0.0-20251121122154-b57c297c6d7a
- github.com/mattermost/mattermost/server/v8 (Go): affected all versions; fixed in 8.0.0-20251121122154-b57c297c6d7a
- github.com/mattermost/mattermost/server/v8 (Go): affected all versions; fixed in 8.0.0-20251121122154-b57c297c6d7a
- 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.4.1
- github.com/mattermost/mattermost-plugin-jira (Go): affected all versions; fixed in 4.4.1
- github.com/mattermost/mattermost-server (Go): affected all versions; no fix listed
- github.com/mattermost/mattermost-server/v5 (Go): affected all versions; no fix listed
- github.com/mattermost/mattermost-server/v6 (Go): affected all versions; no fix listed

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-2025-14273/ (Markdown: https://insights.sbomify.com/CVE-2025-14273/index.md)
```

## Sources

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

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