CVE-2024-6548
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 · uneditedThe Add Admin JavaScript plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.0. 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 confidenceThe Add Admin JavaScript WordPress plugin versions up to 2.0 contains test files that leave PHP's display_errors enabled. When these test files are accessed, PHP outputs full server file paths in error messages, allowing unauthenticated attackers to discover the web application's directory structure.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm plugin installationCheck if the Add Admin JavaScript plugin is present in your WordPress installation by looking in the wp-content/plugins/ directory for a folder named 'add-admin-javascript' or similar variant. You can also check via WP admin under Plugins > Installed Plugins.Affected if The plugin folder exists in your WordPress plugins directory.
-
Identify installed versionOpen the main plugin PHP file (usually add-admin-javascript.php) and look for the version number in the plugin header comment at the top, or check the Version field in the plugin list within WordPress admin panel.Affected if The installed version is 2.0 or lower (any version up to and including 2.0).
-
Locate test files in plugin directoryBrowse the plugin folder using file manager or FTP/SSH and look for files with names containing 'test', 'demo', 'sample', or file extensions such as .php that are not part of the main plugin functionality. Common test file names include test.php, test, php, demo.php, or any file in a 'test' subfolder.Affected if Any test, demo, or sample files exist within the plugin directory.
-
Check PHP display_errors settingCreate a temporary PHP info file (info.php) with content '<?php phpinfo(); ?>' and access it via browser, then search for 'display_errors' in the output. Alternatively, check your php.ini file or runtime PHP configuration for the display_errors directive.Affected if PHP display_errors is set to On or On is found in the display_errors row.
You are affected if the Add Admin JavaScript plugin is installed at version 2.0 or lower, test files exist in the plugin directory, and PHP display_errors is enabled on the server.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate the plugin to a version beyond 2.0 (once available) or remove any test files included with the plugin and ensure PHP's display_errors is disabled in production configurations.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2024-6548 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-6548 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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