dbcve.org
Improper Privilege ManagementWeakness · CWE-269

CVE-2026-2931

HIGH · 8.8 CVSS v3.1 Published 2026-03-26
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 Amelia Booking plugin for WordPress is vulnerable to Insecure Direct Object References in versions up to, and including, 9.1.2. This is due to the plugin providing user-controlled access to objects, letting a user bypass authorization and access system resources. This makes it possible for authenticated attackers with customer-level permissions or above to change user passwords and potentially take over administrator accounts. The vulnerability is in the pro plugin, which has the same slug.

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 Booking plugin for WordPress (pro version) contains an Insecure Direct Object Reference (IDOR) vulnerability allowing authenticated users with customer-level permissions to bypass authorization checks and modify arbitrary user passwords, including administrator accounts.

MitigationUpdate the Amelia Booking plugin to a version beyond 9.1.2, or apply vendor-supplied patch. Verify no unauthorized accounts were created and review user privileges.

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. Verify Amelia Booking plugin is installed
    Log into WordPress admin dashboard and navigate to Plugins > Installed Plugins. Look for 'Amelia' or 'Amelia Booking' in the list. Alternatively, check the wp-content/plugins directory for an amelia folder.
    Affected if The Amelia Booking plugin (pro version) is present in the WordPress installation
  2. Check the installed plugin version
    In WordPress admin, click on the Amelia plugin to view its details and version number. Or open the main plugin PHP file (such as amelia.php or wpamelia.php) in the plugin folder and look for the 'Version' header in the plugin comment block.
    Affected if The version number displayed is 9.1.2 or lower
  3. Confirm WordPress user roles exist
    Navigate to Users > All Users in WordPress admin. Review the list of users and their assigned roles. Note if any users have the 'Customer' role specifically assigned by the Amelia plugin.
    Affected if Customer-level users exist in the WordPress installation and the Amelia plugin is active
  4. Verify API accessibility for user modification
    Inspect network traffic when accessing the Amelia booking pages or use a web vulnerability scanner to test if the user/password modification API endpoints accept requests from authenticated customer-level sessions without proper authorization checks.
    Affected if API endpoints allow customer-level users to submit password reset requests for other user accounts including administrators

The environment is affected if Amelia Booking Pro version 9.1.2 or lower is installed and active, with customer-level user accounts present in the WordPress 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 Booking plugin to a version beyond 9.1.2, or apply vendor-supplied patch. Verify no unauthorized accounts were created and review user privileges.

Recommended fix Moderate confidence

Amelia Booking plugin version 9.1.3 or later (latest available version from the vendor)

  1. Check current Amelia Booking plugin version installed on your WordPress site
  2. Navigate to Plugins > Installed Plugins in WordPress admin dashboard
  3. If the installed version is 9.1.2 or lower, update the Amelia Booking plugin to the latest available version
  4. After updating, verify the plugin version in the plugins list to confirm the update was applied
  5. Ensure WordPress users with 'Customer' role have appropriate permissions - consider reviewing user roles in Users > All Users
  6. Monitor for any suspicious admin account activity following the update
Caveat Review plugin settings after upgrade as minor functionality changes may occur with security updates

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

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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