CVE-2026-4668: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ameliabooking Booking for Appointments and Events Calendar – Amelia
The Amelia Booking for Appointments and Events Calendar WordPress plugin is vulnerable to SQL Injection via the 'sort' parameter in the payments listing endpoint in versions up to 2. 1. 2. This vulnerability arises from insufficient sanitization of the 'sort' parameter, which is directly interpolated into an ORDER BY clause without whitelist validation. Authenticated users with Manager-level access or higher can exploit this flaw to perform time-based blind SQL injection attacks to extract sensitive database information. The vulnerability does not affect availability or integrity but impacts confidentiality. No official patch or fix information is currently available.
AI Analysis
Technical Summary
CVE-2026-4668 describes an SQL Injection vulnerability in the Amelia Booking plugin for WordPress affecting all versions up to 2.1.2. The issue is due to improper neutralization of special elements in the 'sort' parameter used in the payments listing endpoint. The parameter is directly inserted into an ORDER BY clause in the PaymentRepository.php file without sanitization or whitelist validation. PDO prepared statements do not protect column names in ORDER BY clauses, and GET requests bypass nonce validation, allowing authenticated users with 'wpamelia-manager' role or higher to append additional SQL queries. This can lead to extraction of sensitive data via time-based blind SQL injection.
Potential Impact
An attacker with Manager-level or higher privileges can exploit this vulnerability to extract sensitive information from the database through time-based blind SQL injection. The vulnerability impacts confidentiality but does not affect data integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Manager-level access to trusted users only and monitor for suspicious activity related to the payments listing endpoint. Avoid exposing the vulnerable endpoint unnecessarily. Do not rely on PDO prepared statements alone for sanitizing ORDER BY parameters; whitelist validation is required.
CVE-2026-4668: CWE-89 Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') in ameliabooking Booking for Appointments and Events Calendar – Amelia
Description
The Amelia Booking for Appointments and Events Calendar WordPress plugin is vulnerable to SQL Injection via the 'sort' parameter in the payments listing endpoint in versions up to 2. 1. 2. This vulnerability arises from insufficient sanitization of the 'sort' parameter, which is directly interpolated into an ORDER BY clause without whitelist validation. Authenticated users with Manager-level access or higher can exploit this flaw to perform time-based blind SQL injection attacks to extract sensitive database information. The vulnerability does not affect availability or integrity but impacts confidentiality. No official patch or fix information is currently available.
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-4668 describes an SQL Injection vulnerability in the Amelia Booking plugin for WordPress affecting all versions up to 2.1.2. The issue is due to improper neutralization of special elements in the 'sort' parameter used in the payments listing endpoint. The parameter is directly inserted into an ORDER BY clause in the PaymentRepository.php file without sanitization or whitelist validation. PDO prepared statements do not protect column names in ORDER BY clauses, and GET requests bypass nonce validation, allowing authenticated users with 'wpamelia-manager' role or higher to append additional SQL queries. This can lead to extraction of sensitive data via time-based blind SQL injection.
Potential Impact
An attacker with Manager-level or higher privileges can exploit this vulnerability to extract sensitive information from the database through time-based blind SQL injection. The vulnerability impacts confidentiality but does not affect data integrity or availability. There are no known exploits in the wild at this time.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until an official fix is available, restrict Manager-level access to trusted users only and monitor for suspicious activity related to the payments listing endpoint. Avoid exposing the vulnerable endpoint unnecessarily. Do not rely on PDO prepared statements alone for sanitizing ORDER BY parameters; whitelist validation is required.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-03-23T17:43:21.055Z
- Cvss Version
- 3.1
- State
- PUBLISHED
Threat ID: 69cc5aeae6bfc5ba1d4dd37c
Added to database: 3/31/2026, 11:38:18 PM
Last enriched: 4/15/2026, 3:51:36 PM
Last updated: 5/16/2026, 10:34:50 AM
Views: 75
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.