# CVE-2025-5257: Predictable Page Indexing Might Lead to Sensitive Data Exposure

> Unauthenticated attackers can access unpublished page previews via predictable URLs, leading to sensitive data exposure.

- **Severity:** Medium 6.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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:** 28 May 2025
- **Updated:** 28 May 2025
- **Also known as:** CVE-2025-48874, GHSA-cqx4-9vqf-q3m8

## What is CVE-2025-5257?

CVE-2025-5257 is a medium-severity missing authorization vulnerability in Mautic, published on 28 May 2025. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

SummaryThis advisory addresses a security vulnerability in Mautic where unpublished page previews could be accessed by unauthenticated users and potentially indexed by search engines. This could lead to the unintended disclosure of draft content or sensitive information.

Unauthorized Access to Unpublished Page Previews: The page preview functionality for unpublished content, accessible via predictable URLs (e.g., /page/preview/1, /page/preview/2), lacked proper authorization checks. This allowed any unauthenticated user to view content that was not yet intended for public release, and allowed search engines to index these private preview URLs, making the content publicly discoverable.
MitigationMautic has patched this vulnerability by enforcing proper permission checks on preview pages. Users should upgrade to the patched version of Mautic or later.

Weakness: CWE-1284 (Improper Validation of Specified Quantity in Input)

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

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.16 |
| `mautic/core` | Packagist | From 4.0.0 | 4.4.16 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 5.0.0-alpha | 5.2.6 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |
| `mautic/core` | Packagist | From 6.0.0-alpha | 6.0.2 |

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

Upgrade mautic/core to a fixed version for your release line: 4.4.16, 5.2.6 or 6.0.2.

## Is CVE-2025-5257 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-5257 is a medium-severity missing authorization vulnerability in Mautic, published on 28 May 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-5257 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.16
- mautic/core (Packagist): affected from 4.0.0; fixed in 4.4.16
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 5.0.0-alpha; fixed in 5.2.6
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2
- mautic/core (Packagist): affected from 6.0.0-alpha; fixed in 6.0.2

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

## Sources

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

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