dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2025-13842

MEDIUM · 5.3 CVSS v3.1 Published 2026-02-19
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
62/100
Remediation priority · Elevated
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The Breadcrumb NavXT WordPress plugin fails to verify user authorization in its Gutenberg block renderer (render.php), trusting the $_REQUEST['post_id'] parameter directly. This allows unauthenticated attackers to enumerate and view breadcrumb trails for draft or private posts, exposing post titles and hierarchy that should be restricted.

MitigationUpdate to the patched version when released; until then, consider disabling the Gutenberg block or adding firewall rules to restrict access to the affected endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Breadcrumb NavXT is installed
    Locate the plugin directory at wp-content/plugins/breadcrumb-navxt/ and read the main plugin file (usually breadcrumb-navxt.php) to find the version number in the plugin header comment
    Affected if The plugin is installed and the version is lower than the patched version (once released)
  2. Identify if Gutenberg block functionality is active
    Check the plugin files for block registration (look in includes/ or a blocks/ directory for block.json or register_block_type calls) and determine whether the block renderer (render.php) is accessible on the site
    Affected if The Gutenberg block is registered and the render.php endpoint responds to requests without authentication
  3. Test unauthorized post enumeration
    Send a crafted request to the render.php endpoint (typically at /wp-json/bcn/v1/render or similar endpoint using the plugin's block renderer) with a $_REQUEST['post_id'] parameter pointing to a draft or private post ID
    Affected if The endpoint returns breadcrumb trail data (post titles, hierarchy) for posts that should not be accessible to unauthenticated users
  4. Verify access controls are missing
    Review the render.php source code to confirm it does not perform capability checks (like current_user_can('edit_post', $post_id)) or nonce validation before processing the post_id parameter
    Affected if The render.php file lacks authorization checks and directly uses the $_REQUEST['post_id'] value without validation

If Breadcrumb NavXT is installed with an unpatched version, the Gutenberg block is enabled, and the render.php endpoint returns private/draft post breadcrumb data without authentication, the environment is affected.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update to the patched version when released; until then, consider disabling the Gutenberg block or adding firewall rules to restrict access to the affected endpoint.

Recommended fix Moderate confidence

Breadcrumb NavXT 7.5.1 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Breadcrumb NavXT plugin
  4. If an update is available, click 'Update Now' to update to the latest version
  5. Alternatively, manually download the updated plugin from wordpress.org/plugins/breadcrumb-navxt/ and reinstall

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-13842 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-13842 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data