CVE-2025-26965
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 · uneditedAuthorization Bypass Through User-Controlled Key vulnerability in ameliabooking Amelia ameliabooking allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Amelia: from n/a through <= 1.2.16.
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 confidenceAuthorization bypass vulnerability in the Amelia booking WordPress plugin where an attacker can manipulate a user-controlled key to bypass access control checks. The vulnerability stems from incorrectly configured access control security levels, allowing unauthorized access to protected functionality.
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 checksWork through these to decide whether this CVE applies to you.
-
Identify Amelia plugin versionNavigate to WordPress Admin > Plugins > Installed Plugins > Amelia and note the version number, or inspect the main plugin file at wp-content/plugins/amelia/amelia.php for the Version headerAffected if The installed version is unpatched and matches the vulnerable release range
-
Confirm booking functionality is enabledAccess the WordPress frontend and verify if the Amelia booking calendar or appointment scheduling features are published and publicly accessibleAffected if Booking-related endpoints are exposed and accessible to unauthenticated users
-
Locate authorization logic using user-controlled keysInspect plugin PHP files for functions that perform access control checks. Search for patterns where request parameters (such as $_GET, $_POST, or query string values containing 'key', 'token', or 'id') are used directly in permission validation without proper server-side verificationAffected if Authorization logic relies on user-supplied values (keys, tokens, or IDs) that can be manipulated to bypass access control
-
Identify affected API endpointsUse browser developer tools or a proxy to observe which AJAX or REST API endpoints the plugin exposes for booking operations. Check if these endpoints validate user permissions server-side or accept user-controlled keys for authorizationAffected if Protected booking endpoints accept user-controlled keys without validating user permissions server-side
If the Amelia plugin is installed with vulnerable version and its booking endpoints are accessible with user-controlled authorization keys that bypass proper permission checks, the environment is affected by this authorization bypass.
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 fix access control logic across all endpoints, implement proper authorization checks using user-controlled keys, and ensure all sensitive operations validate user permissions server-side.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-26965 — 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-2025-26965 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