dbcve.org
Information ExposureWeakness · CWE-200

CVE-2024-6552

MEDIUM · 5.3 CVSS v3.1 Published 2024-08-08
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 Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.2. This is due to the plugin utilizing Symfony and leaving display_errors on within test files. 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 Amelia WordPress plugin is vulnerable to Full Path Disclosure due to Symfony test files leaving display_errors enabled. Unauthenticated attackers can access these test files to retrieve the server's full filesystem path, which aids in reconnaissance for chained attacks.

MitigationDisable display_errors in PHP configuration or remove test files from production, or update to a patched plugin version when 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. Check if Amelia plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Amelia' or check the plugin files in /wp-content/plugins/amelia/ directory. Look for a version number in the plugin header or readme.txt
    Affected if Amelia plugin is installed and running on the WordPress site
  2. Identify the installed Amelia version
    Open the main plugin file (usually amelia.php or class-amelia.php) and look for 'Version:' in the file header, or check readme.txt for the version number
    Affected if Version cannot be determined or is within any affected range (plugin versions with exposed test files)
  3. Locate Symfony test files in the plugin directory
    Check for test files in the plugin directory, specifically looking for paths like /wp-content/plugins/amelia/vendor/symfony/*/Tests/ or similar test directories under the Symfony vendor folder. Use command: find /path/to/wordpress/wp-content/plugins/amelia -name '*Test.php' -o -name 'test*' 2>/dev/null
    Affected if Any Symfony test files exist in publicly accessible paths within the plugin
  4. Verify test files are web-accessible
    Attempt to access suspected test file paths via HTTP request, for example: curl -I https://yourdomain.com/wp-content/plugins/amelia/vendor/symfony/[component]/Tests/[file].php - or check if these paths respond to web requests
    Affected if Test files are accessible via web requests (HTTP returns 200 OK instead of 403/404)
  5. Check PHP display_errors configuration
    Check phpinfo() output or php.ini for display_errors setting: Look for 'display_errors = On' in PHP configuration. Can be checked via: php -i | grep display_errors or by creating a PHP info file
    Affected if display_errors is set to On in PHP configuration

The environment is affected if the Amelia plugin is installed, Symfony test files exist and are web-accessible, AND PHP display_errors is enabled, allowing unauthenticated attackers to discover the server's 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.

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

Disable display_errors in PHP configuration or remove test files from production, or update to a patched plugin version when available.

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