dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6549

MEDIUM · 5.3 CVSS v3.1 Published 2024-07-27
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 Admin Post Navigation plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.1. This is due to the plugin utilizing bootstrap and leaving test files with display_errors on. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 Admin Post Navigation WordPress plugin versions up to 2.1 contains test files with PHP's display_errors enabled, which are accessible via the web. When these test files are accessed, they output PHP error messages revealing the full server path to the WordPress installation. This information disclosure is passive but can aid attackers in crafting subsequent attacks by revealing directory structures.

MitigationUpdate the plugin to the latest version once available, or disable PHP display_errors in the plugin's test files, remove accessible test files, and ensure proper error handling in the bootstrap process.

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. Identify if Admin Post Navigation plugin is installed
    Check your WordPress plugins directory (wp-content/plugins/) for a folder named 'admin-post-navigation' or similar. In WordPress admin, go to Plugins > Installed Plugins and look for 'Admin Post Navigation' in the list.
    Affected if The plugin is present in the plugins directory or listed in WordPress admin
  2. Determine the installed version of the plugin
    In WordPress admin, find the Admin Post Navigation plugin in the Plugins list and check the version number displayed beneath the plugin name. Alternatively, inspect the plugin's main PHP file header for the 'Version' tag.
    Affected if The version is 2.1 or lower, or if no version number is displayed (which may indicate an unversioned or modified copy)
  3. Locate accessible test files in the plugin directory
    Use a file browser or FTP to navigate to the plugin directory (wp-content/plugins/admin-post-navigation/). Look for files with names containing 'test', 'debug', 'sample', or '.php' files in subdirectories named 'tests', 'test', 'example', or 'demo'.
    Affected if Test, debug, or example PHP files exist and are accessible via HTTP requests to your site
  4. Check if error messages reveal server paths
    Attempt to access any found test files via a web browser (e.g., visit yoursite.com/wp-content/plugins/admin-post-navigation/[testfilename].php). Look for PHP error messages that contain absolute server paths like '/var/www/' or 'C:\inetpub\'.
    Affected if Accessing the test files outputs PHP error messages that display the full server filesystem path

You are affected if the Admin Post Navigation plugin version 2.1 or lower is installed AND accessible test files exist that display PHP error messages revealing server paths.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once available, or disable PHP display_errors in the plugin's test files, remove accessible test files, and ensure proper error handling in the bootstrap process.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6549 — 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-2024-6549 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