dbcve.org
AmeliaWordPress extension · Tms Outsource

CVE-2024-22298

CRITICAL · 9.8 CVSS v3.1 Published 2024-06-10
Fix available
A fix is available. Upgrade to 1.0.99 or later.
See remediation →
100/100
Remediation priority · Urgent
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
Missing Authorization vulnerability in TMS Amelia ameliabooking.This issue affects Amelia: from n/a through 1.0.98.

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 confidence

A missing authorization vulnerability exists in the Amelia booking plugin (ameliabooking) affecting versions through 1.0.98. This critical severity flaw (CVSS 9.8) allows unauthenticated or unauthorized users to access sensitive functionalities or perform actions that should require proper authentication and authorization checks.

MitigationUpdate Amelia booking plugin to the latest patched version immediately. Review and enforce proper authorization controls on all sensitive endpoints and administrative functions.

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.0.99

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
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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. Locate the Amelia plugin installation
    Check the WordPress plugins directory (wp-content/plugins/ameliabooking) for the plugin folder, or view the installed plugins list in the WordPress admin dashboard under Plugins > Installed Plugins
    Affected if The Amelia plugin folder or entry exists in the WordPress installation
  2. Identify the installed Amelia version
    Check the plugin header in ameliabooking/ameliabooking.php for the 'Version' comment, or view the version displayed in the WordPress admin plugins list
    Affected if The reported version number is below 1.0.99 (for example, 1.0.98, 1.0.97, etc.)
  3. Confirm plugin is active
    In WordPress admin, verify that the Amelia plugin status shows as 'Active' under Plugins > Installed Plugins
    Affected if The plugin is installed AND active AND the version is below 1.0.99
  4. Check for unauthorized endpoint exposure
    Test access to common Amelia admin endpoints (such as /wp-admin/admin-ajax.php?action=wpamelia_api&api=/{endpoint}) without providing authentication credentials to see if the API responds without authorization errors
    Affected if API endpoints respond with successful data instead of requiring authentication

The environment is affected if the Amelia booking plugin version is 1.0.98 or any earlier version and the plugin is active in WordPress.

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 1.0.99 or later
Fixed in 1.0.99
Interim mitigation

Update Amelia booking plugin to the latest patched version immediately. Review and enforce proper authorization controls on all sensitive endpoints and administrative functions.

Recommended fix High confidence

Amelia version 1.0.99 or later

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Navigate to WordPress admin dashboard > Plugins
  3. 3. Find the Amelia plugin in the installed plugins list
  4. 4. Click 'Update Now' if an update is available, or manually upload version 1.0.99 or later from the WordPress plugin repository
  5. 5. Verify the update completed successfully by checking the plugin version
  6. 6. Test that booking functionality works correctly after the update

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

Fix this in Amelia Scoped from the published advisory
  • Consultation2.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,980
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,768.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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