dbcve.org
Authorization Bypass (IDOR)Weakness · CWE-639

CVE-2026-5465

HIGH · 8.8 CVSS v3.1 Published 2026-04-07
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 Insecure Direct Object Reference in all versions up to, and including, 2.1.3. This is due to the `UpdateProviderCommandHandler` failing to validate changes to the `externalId` field when a Provider (Employee) user updates their own profile. The `externalId` maps directly to a WordPress user ID and is passed to `wp_set_password()` and `wp_update_user()` without authorization checks. This makes it possible for authenticated attackers, with Provider-level (Employee) access and above, to take over any WordPress account — including Administrator — by injecting an arbitrary `externalId` value when updating their own provider profile.

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 Booking for Appointments and Events Calendar – Amelia plugin for WordPress contains an Insecure Direct Object Reference (IDOR) vulnerability in the UpdateProviderCommandHandler. The handler fails to validate the externalId field when a Provider (Employee) user updates their profile. The externalId maps directly to a WordPress user ID and is passed to wp_set_password() and wp_update_user() without authorization checks, allowing authenticated Provider-level users to inject any externalId value and take over arbitrary WordPress accounts.

MitigationUpdate the Amelia plugin to a version beyond 2.1.3 which includes proper authorization checks and input validation on the externalId field in the UpdateProviderCommandHandler, preventing users from modifying externalId values that map to other WordPress users.

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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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. Identify if Amelia plugin is installed
    Navigate to WordPress admin dashboard > Plugins and locate 'Booking for Appointments and Events Calendar - Amelia' or check plugin files in wp-content/plugins/ameliabooking
    Affected if The Amelia plugin is installed and active
  2. Determine installed plugin version
    In WordPress admin > Plugins > Amelia > View Details, or inspect the main plugin file (e.g., ameliabooking/ameliabooking.php) for the 'Version' header comment
    Affected if Version is 2.1.3 or earlier (versions beyond 2.1.3 contain the fix)
  3. Check for Provider-level user accounts
    In WordPress admin > Users, look for users with the 'Amelia Provider' role, or query the wp_usermeta table for meta_key containing 'amelia_provider'
    Affected if There are users with Provider role in the system
  4. Verify if externalId modification is possible
    Attempt to access the UpdateProviderCommandHandler endpoint (typically via /wp-json/amelia/v1/provider/update) and inspect whether the externalId parameter can be modified in a profile update request
    Affected if The handler accepts and processes externalId values without validating ownership or authorization
  5. Audit user account modifications
    Review WordPress user logs, Amelia booking logs, or database records in wp_usermeta for unexpected password resets or profile changes on user IDs that do not match the requester's ID
    Affected if There are password or profile changes on WordPress user IDs that differ from the authenticated Provider's user ID

You are affected if the Amelia plugin version is 2.1.3 or earlier, Provider-level users exist in the system, and the UpdateProviderCommandHandler allows modification of externalId values to point to arbitrary WordPress user IDs without authorization.

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

Update the Amelia plugin to a version beyond 2.1.3 which includes proper authorization checks and input validation on the externalId field in the UpdateProviderCommandHandler, preventing users from modifying externalId values that map to other WordPress users.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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