# CVE-2024-2731: Improper Access Control Issues Lead to Sensitive Data Exposure in Mautic

> Low-privilege users can view sensitive company and user data and edit tag descriptions due to improper access control in Mautic.

- **Severity:** Medium 5.4 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 1 Aug 2024
- **Also known as:** GHSA-hh28-wc7c-m2r4

## What is CVE-2024-2731?

CVE-2024-2731 is a medium-severity missing authorization vulnerability in Mautic, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Users with low privileges (all permissions deselected in the administrator permissions settings) can view certain pages that expose sensitive information such as company names, users' names and surnames, stage names, and monitoring campaigns and their descriptions. In addition, unprivileged users can see and edit the descriptions of tags. At the time of publication of the CVE no patch is available.

Weakness: CWE-284 (Improper Access Control)

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


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

No fix has been published for CVE-2024-2731 yet. Limit exposure of the affected software until one is available.

## Is CVE-2024-2731 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2731 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2731 is a medium-severity missing authorization vulnerability in Mautic, published on 10 Apr 2024. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2731 exists.

Affected product: Mautic. No package-level version data is available, so check the vendor advisory linked from the reference page.

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

## Sources

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

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