CVE-2026-24967
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 · uneditedMissing Authorization vulnerability in ameliabooking Amelia ameliabooking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Amelia: from n/a through <= 1.2.38.
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 confidenceMissing authorization vulnerability in Amelia Booking plugin <= 1.2.38 allows exploiting incorrectly configured access control security levels, potentially enabling unauthorized users to access privileged functionality or sensitive data that should be restricted.
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
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Amelia Booking plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and look for 'Amelia Booking' or check wp-content/plugins/ directory for amelia-booking folderAffected if Plugin is installed and active
-
Check installed plugin versionIn WordPress admin plugins list, find Amelia Booking and note the version number displayed, or read version from plugin's main PHP file headerAffected if Version is 1.2.38 or lower
-
Identify exposed admin endpointsReview the site's REST API routes by accessing /wp-json/ and look for amelia endpoints, or check .htaccess/nginx config for direct access to wp-content/plugins/amelia-booking/ folderAffected if Amelia REST API endpoints are accessible without authentication or admin nonce verification
-
Verify user role permissionsCheck WordPress user roles at Users > Roles and confirm if any custom Amelia roles exist with elevated capabilities, or inspect amelia-booking/src/Classes/permissions config filesAffected if Non-admin users have privileges that should be restricted according to plugin documentation
-
Test access to sensitive functionsSend a direct POST request to amelia-api endpoints (such as /wp-json/amelia/v1/appointments or /wp-json/amelia/v1/users) using a low-privilege or unauthenticated accountAffected if Requests succeed without proper authorization headers or return sensitive data
If Amelia Booking plugin version 1.2.38 or lower is installed AND sensitive endpoints are accessible without proper admin-level authorization, the environment is affected by this CVE.
Generated from the published advisory. Verify against your own configuration.
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 dataReview and enforce proper authorization checks on all sensitive endpoints and functions within the plugin, ensuring access control configurations are correctly implemented according to the plugin's security model.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-24967 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-24967 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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