CVE-2024-6546
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 One Click Close Comments plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 2.7.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 · moderate confidenceThe One Click Close Comments WordPress plugin (versions up to 2.7.1) is vulnerable to Full Path Disclosure. The vulnerability exists because the plugin utilizes bootstrap and leaves test files with PHP's display_errors setting enabled, allowing unauthenticated attackers to retrieve the absolute filesystem path of the web application.
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.
-
Check One Click Close Comments plugin versionNavigate to WordPress admin dashboard > Plugins and locate 'One Click Close Comments' to view the installed version numberAffected if Version is 2.7.1 or lower
-
Verify PHP display_errors settingCheck your php.ini file for 'display_errors = On', or create a temporary phpinfo() page to view the current PHP configuration, or inspect .htaccess and wp-config.php for any display_errors directivesAffected if display_errors is enabled (set to On)
-
Identify test files in the plugin directoryUse FTP, SSH, or your hosting file manager to browse to wp-content/plugins/one-click-close-comments/ and list all files, looking for test files such as test.php, test_*.php, or any file with 'test' in the nameAffected if Any test files exist in the plugin directory
You are affected if the plugin version is 2.7.1 or lower AND PHP display_errors is enabled AND test files are present in the plugin directory.
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.
dbcve · scopedUpdate the plugin to the latest patched version once available, or remove the plugin if no patch exists. Alternatively, disable PHP display_errors in php.ini or web server configuration to prevent path disclosure.
- Locate and delete any test files in the plugin directory that may contain debug code or leftover scripts
- Ensure PHP display_errors is disabled in php.ini by setting display_errors = Off
- Alternatively, add ini_set('display_errors', 0); to the plugin's main PHP file to disable error display at runtime
- Verify the changes by attempting to trigger a PHP error on the site and confirming no path information is revealed
- If available, upgrade the One Click Close Comments plugin to the latest version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.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,456.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-6546 — 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-6546 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