dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6545

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 Trim Interface plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 3.5.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 Trim Interface WordPress plugin up to version 3.5.1 is vulnerable to Full Path Disclosure. The vulnerability exists because the plugin utilizes bootstrap and leaves test files with display_errors enabled, causing the web server to output the full filesystem path when certain error conditions are triggered. Unauthenticated attackers can exploit this to reveal the absolute path of the WordPress installation.

MitigationDisable PHP display_errors in the server configuration (php.ini or .htaccess) and remove any test files shipped with the plugin that may have debug output enabled. Alternatively, update to a patched version if available.

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. Verify Admin Trim Interface plugin is installed
    Check the WordPress plugin directory for the Admin Trim Interface plugin folder. In wp-content/plugins/, look for a folder named 'admin-trim-interface' or similar. Check the plugin's main PHP file for the version number in the plugin header.
    Affected if The plugin is present in the WordPress installation.
  2. Check installed plugin version against affected range
    Open the main plugin file (usually admin-trim-interface.php) and locate the 'Version' field in the plugin header comment at the top. Compare this version number to 3.5.1.
    Affected if The installed version is 3.5.1 or lower.
  3. Identify test files shipped with the plugin
    List all files in the plugin directory (wp-content/plugins/admin-trim-interface/). Look for any files with names containing 'test', 'debug', 'sample', or '.php' files that are not the main plugin files.
    Affected if Test files, debug scripts, or sample files exist in the plugin folder.
  4. Verify PHP display_errors configuration
    Check the PHP configuration by creating a temporary PHP info file (phpinfo.php) or inspecting php.ini, .htaccess, or wp-config.php for the setting 'display_errors = On'. Also check for any .htaccess rules in the plugin directory that may enable error display.
    Affected if display_errors is set to On in PHP configuration or .htaccess.
  5. Attempt to trigger full path disclosure
    Send an HTTP request to the plugin's test files (if found) or trigger an error condition by accessing suspected test endpoints. For example, try accessing common test file paths or induce a PHP error through the plugin's bootstrap mechanism.
    Affected if The response contains an absolute filesystem path (e.g., /var/www/html/wp-content/plugins/...).

The environment is affected if the Admin Trim Interface plugin version 3.5.1 or lower is installed, test or debug files exist in the plugin directory, and PHP display_errors is enabled, allowing unauthenticated users to retrieve the full filesystem path.

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

Disable PHP display_errors in the server configuration (php.ini or .htaccess) and remove any test files shipped with the plugin that may have debug output enabled. Alternatively, update to a patched version if available.

Recommended fix Moderate confidence

3.5.2

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Admin Trim Interface' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. Alternatively, manually download the updated plugin from the WordPress plugin repository and upload via Plugins > Add New > Upload Plugin
  6. 6. Verify the plugin is running version 3.5.2 or higher after updating

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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