# CVE-2025-13828: Mautic user without privileged access to the Marketplace can install and uninstall composer packages

> Low-privileged users can install malicious packages via Composer to gain higher privileges, bypassing authorization checks.

- **Severity:** Critical 9.0 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 2 Dec 2025
- **Updated:** 2 Dec 2025
- **Also known as:** GHSA-3fq7-c5m8-g86x

## What is CVE-2025-13828?

CVE-2025-13828 is a critical missing authorization vulnerability in Mautic, published on 2 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SummaryA non privileged user can install and remove arbitrary packages via composer for a composer based installed, even if the flag in update settings for enable composer based update is unticked.

ImpactA low-privileged user of the platform can install malicious code to obtain higher privileges.

Weakness: CWE-862 (Missing Authorization)

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

6 open source packages ship an affected version, including mautic/core.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mautic/core` | Packagist | From 4.0.0 | 4.4.18 |
| `mautic/core` | Packagist | From 4.0.0 | 4.4.18 |
| `mautic/core` | Packagist | From 5.0.0 | 5.2.9 |
| `mautic/core` | Packagist | From 5.0.0 | 5.2.9 |
| `mautic/core` | Packagist | From 6.0.0 | 6.0.7 |
| `mautic/core` | Packagist | From 6.0.0 | 6.0.7 |

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

Upgrade mautic/core to a fixed version for your release line: 4.4.18, 5.2.9 or 6.0.7.

## Is CVE-2025-13828 being exploited?

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

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-13828 and fix it if it is affected.

What it is: CVE-2025-13828 is a critical missing authorization vulnerability in Mautic, published on 2 Dec 2025. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2025-13828 in the wild and no public exploit code.

Affected packages and fixed versions:
- mautic/core (Packagist): affected from 4.0.0; fixed in 4.4.18
- mautic/core (Packagist): affected from 4.0.0; fixed in 4.4.18
- mautic/core (Packagist): affected from 5.0.0; fixed in 5.2.9
- mautic/core (Packagist): affected from 5.0.0; fixed in 5.2.9
- mautic/core (Packagist): affected from 6.0.0; fixed in 6.0.7
- mautic/core (Packagist): affected from 6.0.0; fixed in 6.0.7

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

## Sources

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

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