# CVE-2025-13842: Breadcrumb NavXT <= 7.5.0 - Missing Authorization to Sensitive Information Exposure

> Unauthenticated attackers can view breadcrumb trails for private or draft posts by manipulating the post_id parameter, exposing sensitive post titles and hierarchy.

- **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:** 19 Feb 2026
- **Updated:** 8 Apr 2026
- **Also known as:** GHSA-qqx4-ccm8-48mc

## What is CVE-2025-13842?

CVE-2025-13842 is a medium-severity missing authorization vulnerability in mtekk Breadcrumb NavXT, published on 19 Feb 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

The Breadcrumb NavXT plugin for WordPress is vulnerable to authorization bypass through user-controlled key in versions up to and including 7.5.0. This is due to the Gutenberg block renderer trusting the $_REQUEST['post_id'] parameter without verification in the includes/blocks/build/breadcrumb-trail/render.php file. This makes it possible for unauthenticated attackers to enumerate and view breadcrumb trails for draft or private posts by manipulating the post_id parameter, revealing post titles and hierarchy that should remain hidden.

Weakness: CWE-639 (Authorization Bypass Through User-Controlled Key)

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


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

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

## Is CVE-2025-13842 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2025-13842 is a medium-severity missing authorization vulnerability in mtekk Breadcrumb NavXT, published on 19 Feb 2026. 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-13842 in the wild and no public exploit code.

Affected product: mtekk Breadcrumb NavXT. 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-2025-13842/ (Markdown: https://insights.sbomify.com/CVE-2025-13842/index.md)
```

## Sources

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

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