Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Subscriber-level account required (PR:L), network-accessible plugin endpoint (AV:N), no confidentiality or availability impact - only data integrity manipulation.
Primary rating from Vendor (Patchstack).
CVSS VectorVendor: Patchstack
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:N
Lifecycle Timeline
1DescriptionCVE.org
Subscriber Broken Access Control in Amelia <= 2.2 versions.
AnalysisAI
Broken access control in the Amelia booking plugin for WordPress (versions up to and including 2.2) allows low-privileged subscriber-level users to perform unauthorized high-integrity actions within the booking system. The flaw stems from missing authorization checks (CWE-862), permitting registered users - typically clients or end-users of the booking portal - to interact with data or functionality restricted to higher roles such as managers or administrators. No public exploit has been identified at time of analysis, and KEV listing is absent, but the low attack complexity and network accessibility make this a straightforward target once a subscriber account is obtained.
Technical ContextAI
Amelia is a WordPress appointment and event booking plugin developed by TMS (CPE: cpe:2.3:a:tms:amelia:*:*:*:*:*:*:*:*). It implements role-based access control across WordPress user roles (subscriber, employee, manager, admin). CWE-862 (Missing Authorization) indicates that one or more REST API endpoints or AJAX handlers within Amelia fail to validate whether the authenticated user holds the minimum required capability before processing a privileged request. In WordPress, the subscriber role is the lowest registered role, granted automatically to any site visitor who creates an account. The CVSS vector (PR:L) confirms that exploitation requires only this minimal authentication level. The integrity impact (I:H) without confidentiality impact (C:N) suggests the flaw enables data manipulation - such as creating, modifying, or canceling bookings that belong to other users or elevating booking permissions - rather than data disclosure.
RemediationAI
The primary remediation is to upgrade the Amelia plugin to a version above 2.2. No exact patched version number is confirmed in the available intelligence data - the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/ameliabooking/vulnerability/wordpress-amelia-plugin-2-2-broken-access-control-vulnerability) should be consulted to confirm the specific fixed release before upgrading. As a compensating control where immediate upgrade is not possible, site administrators should disable open user registration (Settings > General > uncheck 'Anyone can register') to prevent untrusted parties from obtaining subscriber accounts, noting this will prevent new users from self-registering. Additionally, a Web Application Firewall (WAF) rule targeting unauthorized Amelia REST or AJAX endpoints can reduce exposure, though this requires precise endpoint identification. Both workarounds carry operational trade-offs and do not address the underlying authorization defect.
The Amelia WordPress plugin before 1.0.47 stores image blobs into actual files whose extension is controlled by the user
The Amelia WordPress plugin before 1.0.47 does not sanitize and escape the code parameter before outputting it back in a
Missing Authorization vulnerability in TMS Amelia ameliabooking.0.98. Rated critical severity (CVSS 9.8), this vulnerabi
The Amelia WordPress plugin before 1.0.48 does not have proper authorisation when handling Amelia SMS service, allowing
The Amelia WordPress plugin before 1.0.49 does not have proper authorisation when managing appointments, allowing any cu
The Amelia WordPress plugin before 1.0.47 does not have proper authorisation when managing appointments, allowing any cu
Blind SQL injection in the Amelia booking plugin for WordPress (Melograno Venture Studio) affects all versions from unkn
Privilege escalation in the Amelia booking plugin for WordPress (versions 2.3 and earlier) allows an authenticated low-p
The Amelia WordPress plugin before 1.0.47 does not have CSRF check in place when deleting customers, which could allow a
Blind SQL injection in Amelia WordPress plugin (ameliabooking) version 2.1.1 and earlier allows authenticated privileged
Unauthenticated sensitive data exposure in the Amelia (Amelia Booking) WordPress plugin versions 2.2 and earlier allows
The Amelia WordPress plugin is vulnerable to Cross-Site Scripting due to insufficient escaping and sanitization of the l
Same weakness CWE-862 – Missing Authorization
View allSame technique Authentication Bypass
View allShare
External POC / Exploit Code
Leaving vuln.today
EUVD-2026-36998
GHSA-rqrh-627v-hmpc