dbcve.org
AmeliaWordPress extension · Tmsproducts

CVE-2024-6332

MEDIUM · 6.5 CVSS v3.1 Published 2024-09-05
Fix available
A fix is available. Upgrade to after 7.7 or later.
See remediation →
74/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 Premium and Lite plugins for WordPress are vulnerable to unauthorized access of data due to a missing capability check on the 'ameliaButtonCommand' function in all versions up to, and including, Premium 7.7 and Lite 1.2.4. This makes it possible for unauthenticated attackers to access employee calendar details, including Google Calendar OAuth tokens in the premium version.

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 has a missing capability check on the 'ameliaButtonCommand' function, allowing unauthenticated attackers to access employee calendar details including Google Calendar OAuth tokens in the Premium version. This is a Broken Access Control vulnerability where an API endpoint lacks authorization validation.

MitigationUpdate the Amelia plugin to versions beyond Premium 7.7 and Lite 1.2.4 to receive the vendor patch, or implement proper WordPress capability checks (e.g., current_user_can()) on the ameliaButtonCommand function.

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
AmeliaWordPress extension
Affected:<= 1.2.3<= 7.7

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
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/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. Identify Amelia plugin installation and version
    In WordPress admin, go to Plugins > Installed Plugins and locate Amelia. The version number is displayed under the plugin name. Alternatively, check the plugin header in wp-content/plugins/ameliabooking/ameliabooking.php for the Version defined.
    Affected if The installed version is 1.2.3 or lower (Lite version) OR 7.7 or lower (Premium version)
  2. Confirm plugin type (Lite vs Premium)
    Check if the Premium version of Amelia is installed. Premium installations typically have the ameliabooking-premium folder in wp-content/plugins/ or display 'Premium' in the plugin description. Lite versions do not include calendar integration features.
    Affected if Premium version 7.7 or lower is installed, as this version contains the Google Calendar OAuth token exposure vulnerability
  3. Verify API endpoint accessibility
    Send a direct HTTP request to the ameliaButtonCommand endpoint without providing authentication credentials. The endpoint typically responds at /wp-json/amelia/v1/booking/button or similar /wp-json/amelia/ routes. Check if the server returns calendar-related data without requiring a logged-in session.
    Affected if The API endpoint returns employee calendar details or Google Calendar OAuth tokens without requiring WordPress user authentication
  4. Check for exposed Google Calendar credentials
    If the API is accessible, inspect any returned data structures for Google Calendar OAuth tokens, API keys, or calendar credentials associated with employee accounts. These would appear in the response payload under fields related to google_calendar or oauth tokens.
    Affected if Calendar data returned from the unauthenticated endpoint contains Google Calendar OAuth tokens, API credentials, or other sensitive calendar integration details

A user is affected if the Amelia plugin version is 1.2.3 or lower (Lite) or 7.7 or lower (Premium) AND the ameliaButtonCommand API endpoint is accessible without authentication, potentially exposing employee calendar data including Google Calendar OAuth tokens in Premium installations.

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 7.7
Interim mitigation

Update the Amelia plugin to versions beyond Premium 7.7 and Lite 1.2.4 to receive the vendor patch, or implement proper WordPress capability checks (e.g., current_user_can()) on the ameliaButtonCommand function.

Recommended fix Moderate confidence

Amelia Lite 1.2.5 or later; Amelia Premium 7.8 or later

  1. Log in to the WordPress admin dashboard
  2. Navigate to Plugins > Installed Plugins
  3. Find the Amelia plugin (Lite or Premium version)
  4. Deactivate the current version
  5. Delete the current version
  6. Click 'Add New' and upload/install the updated version from the official WordPress plugin repository or your purchase source
  7. Activate the new version
  8. Verify the plugin functions correctly by testing the booking functionality
Caveat Standard minor version upgrade - review release notes for any behavior changes

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

Fix this in Amelia Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
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,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-6332 — 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-6332 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