# CVE-2022-25768: Improper Access Control in UI upgrade process

> Attackers can access version info or execute upgrade tasks without permission due to missing access controls in the UI upgrade process.

- **Severity:** High 7.0 (`CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:L/I:L/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 18 Sep 2024
- **Updated:** 19 Sep 2024
- **Also known as:** GHSA-x3jx-5w6m-q2fc

## What is CVE-2022-25768?

CVE-2022-25768 is a high-severity missing authorization vulnerability in Mautic, published on 18 Sep 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The logic in place to facilitate the update process via the user interface lacks access control to verify if permission exists to perform the tasks. Prior to this patch being applied it might be possible for an attacker to access the Mautic version number or to execute parts of the upgrade process without permission. As upgrading in the user interface is deprecated, this functionality is no longer required.

Weakness: CWE-862 (Missing Authorization), CWE-287 (Improper Authentication)

## Which versions are affected by CVE-2022-25768?

8 open source packages ship an affected version, including mautic/core and mautic/core-lib. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `mautic/core` | Packagist | From 1.1.3 | 4.4.13 |
| `mautic/core` | Packagist | From 1.1.3 | 4.4.13 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.1.1 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.1.1 |
| `mautic/core-lib` | Packagist | From 1.1.3 | 4.4.13 |
| `mautic/core-lib` | Packagist | From 1.1.3 | 4.4.13 |
| `mautic/core-lib` | Packagist | From 5.0.0-alpha | 5.1.1 |
| `mautic/core-lib` | Packagist | From 5.0.0-alpha | 5.1.1 |

Products: Acquia Mautic.

## How do I fix CVE-2022-25768?

Upgrade mautic/core to a fixed version for your release line: 4.4.13 or 5.1.1.

## Is CVE-2022-25768 being exploited?

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

## Other vulnerabilities in Mautic

- [CVE-2022-25772](https://insights.sbomify.com/CVE-2022-25772/): Cross-site Scripting vulnerability in Mautic's tracking pixel functionality (critical 9.6)
- [CVE-2020-35125](https://insights.sbomify.com/CVE-2020-35125/): Mautic is vulnerable to XSS vulnerability (critical 9.6)
- [CVE-2020-35124](https://insights.sbomify.com/CVE-2020-35124/): XSS vulnerability leveraged through referrers could allow un-authorized admin access in Mautic (critical 9.6)
- [CVE-2024-47051](https://insights.sbomify.com/CVE-2024-47051/): Remote Code Execution & File Deletion in Asset Uploads (critical 9.1)
- [CVE-2020-35128](https://insights.sbomify.com/CVE-2020-35128/): Mautic stored Cross-site Scripting (XSS) (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2022-25768 and fix it if it is affected.

What it is: CVE-2022-25768 is a high-severity missing authorization vulnerability in Mautic, published on 18 Sep 2024. 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-2022-25768 in the wild and no public exploit code.

Affected packages and fixed versions:
- mautic/core (Packagist): affected from 1.1.3; fixed in 4.4.13
- mautic/core (Packagist): affected from 1.1.3; fixed in 4.4.13
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.1.1
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.1.1
- mautic/core-lib (Packagist): affected from 1.1.3; fixed in 4.4.13
- mautic/core-lib (Packagist): affected from 1.1.3; fixed in 4.4.13
- mautic/core-lib (Packagist): affected from 5.0.0-alpha; fixed in 5.1.1
- mautic/core-lib (Packagist): affected from 5.0.0-alpha; fixed in 5.1.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-2022-25768/ (Markdown: https://insights.sbomify.com/CVE-2022-25768/index.md)
```

## Sources

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

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