CVE-2025-2578
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 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.19 via the 'wpAmeliaApiCall' function. 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 Amelia WordPress plugin versions up to 1.2.19 contains a Full Path Disclosure vulnerability in the 'wpAmeliaApiCall' function. Unauthenticated attackers can trigger this function to reveal the full server path to the web application root directory through verbose error messages or debug output.
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 Amelia plugin installation and activation statusInspect the WordPress plugins directory (wp-content/plugins/) for the 'ameliabooking' folder, or check the Plugins page in the WordPress admin dashboard to see if Amelia is installed and active.Affected if The Amelia plugin is present and active on the WordPress site.
-
Identify installed plugin versionOpen the main plugin file (e.g., ameliabooking.php) in the ameliabooking folder and locate the 'Version' header in the plugin comment block, or check the 'Version' field in the plugin list within the WordPress admin.Affected if The installed version is 1.2.19 or lower.
-
Verify presence of vulnerable functionSearch the plugin files (e.g., using grep or a file search) for the string 'wpAmeliaApiCall' within the ameliabooking directory.Affected if The function 'wpAmeliaApiCall' is found in the plugin code.
-
Check unauthenticated access to the functionExamine the plugin's PHP code to see if 'wpAmeliaApiCall' is hooked to an action accessible to unauthenticated users (e.g., via 'add_action' with 'wp_ajax_nopriv_' or a REST API route without authentication).Affected if The function is hooked to a public (non-authenticated) action or endpoint.
If the Amelia plugin is active, version 1.2.19 or lower, and the wpAmeliaApiCall function is publicly accessible, the site is affected by the full path disclosure vulnerability.
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 Amelia plugin to version 1.2.20 or later. As an interim measure, disable the plugin if not needed, or implement WAF rules to filter sensitive path information from HTTP responses.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-2578 — 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-2025-2578 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