dbcve.org
Custom Post LimitsWordPress extension · Coffee2code

CVE-2024-6544

MEDIUM · 5.3 CVSS v3.1 Published 2024-09-13
Fix available
A fix is available. Upgrade to after 4.4.1 or later.
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 Custom Post Limits plugin for WordPress is vulnerable to full path disclosure in all versions up to, and including, 4.4.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 Custom Post Limits WordPress plugin (versions up to 4.4.1) has a full path disclosure vulnerability. The plugin uses bootstrap files and leaves test files accessible with PHP's display_errors enabled, causing the server's full filesystem path to be revealed to unauthenticated attackers. This information disclosure alone causes no direct damage but aids in reconnaissance for chained attacks.

MitigationDisable display_errors in PHP configuration and remove or secure any test files included with the plugin. Update to version 4.4.2 or later if available, or remove the plugin if no update is provided.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Custom Post LimitsWordPress extension
Affected:<= 4.4.1

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 plugin is installed
    Check if the Custom Post Limits plugin (by Coffee2code) is present in your WordPress wp-content/plugins/ directory. Look for a folder named 'custom-post-limits' or similar.
    Affected if The plugin folder exists in the WordPress plugins directory.
  2. Identify installed plugin version
    Open the main plugin file (usually custom-post-limits.php) and look for the version number in the plugin header comment, or check the readme.txt file for the 'Stable tag' entry.
    Affected if The version listed is 4.4.1 or lower.
  3. Check PHP display_errors setting
    Create a PHP info file (phpinfo.php) with content '<?php phpinfo(); ?>' and access it via browser, or check your php.ini for 'display_errors = On'. Alternatively, check if error messages are visible on the site.
    Affected if display_errors is set to On in PHP configuration.
  4. Locate test files included with plugin
    Browse the plugin directory for test files - look for files named test*.php, sample*.php, or any files in a 'tests' or 'test' subdirectory that may have been left accessible.
    Affected if Test files exist in the plugin directory and are publicly accessible.
  5. Verify path disclosure is triggerable
    Attempt to access any identified test files directly via browser URL (e.g., /wp-content/plugins/custom-post-limits/test.php). If the response shows full filesystem paths in error messages, the vulnerability is present.
    Affected if Accessing test files reveals absolute filesystem paths in error output.

You are affected if the Custom Post Limits plugin (version 4.4.1 or lower) is installed AND PHP display_errors is enabled AND test files are accessible, causing full paths to be disclosed.

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
Upgrade available Upgrade to a release after 4.4.1
Interim mitigation

Disable display_errors in PHP configuration and remove or secure any test files included with the plugin. Update to version 4.4.2 or later if available, or remove the plugin if no update is provided.

Recommended fix Moderate confidence

Latest version from wordpress.org/plugins/custom-post-limits/ (any release above 4.4.1)

  1. Check the current version of the Custom Post Limits plugin installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in the WordPress admin dashboard
  3. Locate Custom Post Limits and note the current version
  4. Navigate to Plugins > Add New > Upload Plugin or directly download the latest version from the official WordPress plugin repository at wordpress.org/plugins/custom-post-limits/
  5. Update the plugin to the latest available version (any version higher than 4.4.1)
  6. Verify the update was successful and test that the plugin functionality still works correctly

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

Fix this in Custom Post Limits 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 the upgrade done

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-6544 — 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-6544 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