dbcve.org
Improper AuthorizationWeakness · CWE-285

CVE-2026-6449

MEDIUM · 5.3 CVSS v3.1 Published 2026-05-02
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 Improper Authorization in all versions up to, and including, 2.1.2. This is due to a logical short-circuit flaw in authorization logic that causes token validation to be entirely skipped when a booking has a 'waiting' status. This makes it possible for unauthenticated attackers to approve any booking that is in 'waiting' status by sending a crafted request to the publicly-accessible admin-ajax endpoint.

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 an improper authorization vulnerability where token validation is bypassed for bookings with 'waiting' status. Unauthenticated attackers can approve any waiting booking by sending crafted requests to the publicly accessible admin-ajax endpoint, due to a logical short-circuit flaw in the authorization logic.

MitigationUpdate the Amelia plugin to version 2.1.3 or later, which includes proper token validation regardless of booking status. Until then, consider restricting access to the affected admin-ajax endpoint or monitoring for suspicious approval requests.

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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
    Navigate to WordPress admin dashboard > Plugins and locate the Amelia plugin in the installed plugins list, or inspect the plugin directory /wp-content/plugins/amelia for the existence of the amelia.php or main plugin file.
    Affected if The Amelia plugin is present in the WordPress installation.
  2. Determine installed Amelia version
    In WordPress admin > Plugins, click on the Amelia plugin to view its details and note the version number displayed, or inspect the plugin header in the main PHP file for the 'Version' tag.
    Affected if The installed version is earlier than 2.1.3.
  3. Check for waiting status bookings
    Access the WordPress admin panel and navigate to the Amelia bookings section, or query the WordPress database (typically in a table named wp_amelia_bookings or similar) for records where status = 'waiting'.
    Affected if There are existing bookings with 'waiting' status in the system.
  4. Verify admin-ajax endpoint accessibility
    Test accessing https://yourdomain.com/wp-admin/admin-ajax.php directly without authentication using a browser or curl command. The endpoint is publicly accessible if it responds without requiring login credentials.
    Affected if The admin-ajax.php endpoint is reachable without authentication (default WordPress configuration).
  5. Review logs for suspicious booking approval activity
    Inspect WordPress debug logs, server access logs, or Amelia's internal activity logs for POST requests to admin-ajax.php with action 'amelia_booking_approve' or similar approval-related actions, especially from unauthenticated IP addresses.
    Affected if There are approval requests to admin-ajax from unauthenticated sources or unusual approval patterns.

A user is affected if the Amelia plugin versions earlier than 2.1.3 are installed, the admin-ajax endpoint is publicly accessible, and waiting status bookings exist in the system.

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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Amelia plugin to version 2.1.3 or later, which includes proper token validation regardless of booking status. Until then, consider restricting access to the affected admin-ajax endpoint or monitoring for suspicious approval requests.

Recommended fix Moderate confidence

Upgrade to a version newer than 2.1.2 (check WordPress plugin repository for latest stable release)

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Booking for Appointments and Events Calendar – Amelia' plugin
  4. 4. If an update is available, click 'Update Now' to install the latest version
  5. 5. After updating, verify the plugin version is newer than 2.1.2
  6. 6. Test the booking approval functionality to confirm the authorization fix is working correctly

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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