# CVE-2024-2730: Predictable Page Indexing Might Lead to Sensitive Data Exposure in Mautic

> Unauthenticated attackers can access unpublished landing page content via predictable URLs, exposing sensitive data in Mautic.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 10 Apr 2024
- **Updated:** 9 Aug 2024
- **Also known as:** GHSA-9j6h-484m-x3f5

## What is CVE-2024-2730?

CVE-2024-2730 is a medium-severity vulnerability in Mautic, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Mautic uses predictable page indices for unpublished landing pages, their content can be accessed by unauthenticated users under public preview URLs which could expose sensitive data. At the time of publication of the CVE no patch is available

Weakness: CWE-425 (Direct Request)

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


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

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

## Is CVE-2024-2730 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2024-2730 is a medium-severity vulnerability in Mautic, published on 10 Apr 2024. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2024-2730 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-2730/ (Markdown: https://insights.sbomify.com/CVE-2024-2730/index.md)
```

## Sources

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

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