EUVD-2026-102005
GHSA-2rq8-jj9v-244m
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessIdentify site running Amelia ≤2.4.10
-
ExploitSend crafted request to vulnerable booking endpoint
-
ExecutionInject SQL via unsanitized parameter
-
ImpactExfiltrate WordPress database contents
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A05:2025 - Injection
ASVS 5.0
V1 - Encoding and Sanitization Parameterized queries, prepared statements
MITRE ATT&CK
2 techniques across 2 tactics: Initial Access, Persistence The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitable against any WordPress site running the TMS Amelia (ameliabooking) plugin at version 2.4.10 or earlier; the affected code path is a plugin request parameter reachable over the network. Per the CVSS vector (PR:N/UI:N), no authentication and no user interaction are required, and default configurations appear sufficient since no special feature-enablement condition is stated in the description. The primary limiting factors are therefore version (must be ≤2.4.10) and the plugin being installed and active on an internet-reachable WordPress instance; no non-default setting is documented as a prerequisite. |
| Impact | This is a high-priority vulnerability on paper and likely a genuine one in practice. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes network-reachable, low-complexity, unauthenticated exploitation - the worst-case profile for a public-facing WordPress plugin - and the 9.3 score is driven largely by S:C (scope change) plus C:H. The reporter is Patchstack, a credible WordPress vulnerability intelligence source, which lends confidence to the classification (CWE-89, SQL injection). However, several signals are MISSING and must not be presented as confirmed: no EPSS probability was supplied, there is no CISA KEV listing, and no public exploit/POC is referenced, so this is 'no public exploit identified at time of analysis' rather than active exploitation. Note a vendor-vs-logic tension worth verifying: the input vector sets I:N and A:L, yet SQL injection frequently permits at least limited data modification - treat the integrity impact as vendor-stated, not independently confirmed. Overall: credible, widely-deployed, unauthenticated SQLi deserves prompt patching, but the absence of EPSS/KEV/POC data means the real-world exploitation tempo is currently unknown rather than demonstrably widespread. |
| Exploit ScenarioDerived | A remote, unauthenticated attacker sends a crafted request to a vulnerable Amelia booking endpoint on a public WordPress site, injecting SQL into a parameter that is not properly neutralized. Because the CVSS vector is AV:N/AC:L/PR:N/UI:N, no login or user interaction is required, allowing the attacker to read sensitive database contents (C:H), such as customer booking data and WordPress user/credential tables. No public proof-of-concept is referenced in the provided data at the time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Unauthenticated SQL injection in the TMS Amelia (ameliabooking) plugin for WordPress, affecting all versions through 2.4.10, allows remote attackers to inject arbitrary SQL into database queries executed by the plugin. Per the assessed vector (AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N), no authentication, no user interaction, and no non-default configuration are required - the only prerequisites are that the plugin be installed and active at a version at or below 2.4.10 on a network-reachable WordPress instance, making exposure broad across unpatched booking sites. The impact is confidentiality-focused: the classification indicates high confidentiality impact with no integrity or availability impact, so the practical risk is large-scale extraction of data from the site's WordPress database rather than data destruction or code execution. No public exploit code has been identified at time of analysis and the vulnerability is not listed as confirmed actively exploited (CISA KEV); no EPSS score was available in the source data, but given the unauthenticated, pre-auth access path and the database-level target, this should be treated as high priority on paper.
RemediationAI
No patched version is identified in the available data; the advisory enumerates affected versions through 2.4.10 without specifying a fixed release, so the first action is to confirm the current fixed version in the vendor's changelog and on the Patchstack advisory (https://patchstack.com/database/wordpress/plugin/ameliabooking/vulnerability/wordpress-amelia-plugin-2-4-10-sql-injection-vulnerability?_s_id=cve) and upgrade to the newest Amelia release above 2.4.10 as soon as it is published - do not assume 2.4.11 exists until verified. If the plugin is not actively used for bookings, deactivating and deleting it removes the attack surface entirely; the trade-off is loss of booking/appointment functionality and any stored booking data remains in the database unless cleaned. Where an immediate update is not possible, place the site behind a WAF or reverse proxy with virtual patching that blocks SQL metacharacters and injection patterns (UNION, SLEEP, stacked queries, quote/comment sequences) on requests to plugin endpoints such as admin-ajax.php, the plugin's REST routes and any public booking forms; expect false positives on legitimate free-text fields, which may need tuning, and treat this as a stopgap because WAF normalization bypasses are common. Additionally, restrict the WordPress database user to the minimum privileges the site needs (no FILE, no cross-schema grants) so a successful injection cannot be leveraged for file read or writes to other databases, remove or deactivate unused plugins to shrink the shared-schema blast radius, and enable request logging plus database query monitoring to detect extraction attempts. If exploitation is suspected, rotate database credentials and WordPress salts, force password resets for all users (wp_users hashes are directly exposed by a confidentiality-only SQL injection), and review booking/customer PII for exfiltration.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 1 package in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The root cause is CWE-89, Improper Neutralization of Special Elements used in an SQL Command, classically a failure to parameterize or escape user-supplied input before it is concatenated into a SQL statement. In a WordPress plugin such as Amelia, which manages bookings, appointments, services, employees and customer records, request parameters handled by plugin code are passed through $wpdb queries; when a parameter is interpolated directly instead of being passed through $wpdb->prepare() or a strictly validated cast, an attacker can append SQL syntax that alters the executed statement. The assessed CVSS vector marks Scope Changed (S:C) with Confidentiality High and Integrity/Availability None, which is consistent with an injection that can reach data beyond the plugin's own tables - for example wp_users, wp_usermeta, options and other plugins' tables in the same database schema - while not being characterized as enabling arbitrary writes or denial of service. The vulnerability is reported by Patchstack (audit@patchstack.com), a third-party WordPress plugin vulnerability database, and no CPE strings were supplied in the source data, so affected-version identification rests on the plugin slug/name (ameliabooking) and the stated version ceiling of 2.4.10. The PR:N and UI:N values confirm this is reachable remotely without credentials or victim interaction.
Know when Wordpress Plugin gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
Unauthenticated network SQLi against a WordPress plugin gives AV:N/AC:L/PR:N/UI:N and C:H; S:C reflects the separate database component, and I/A kept conservative (N) absent evidence of write or DoS impact.
Primary rating from Vendor (patchstack).
CVSS VectorVendor: patchstack
DescriptionCVE.org
Improper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in TMS Amelia ameliabooking allows SQL Injection.This issue affects Amelia: from n/a through 2.4.10.
Articles & Coverage 1
Executive ViewAI
A critical unauthenticated SQL injection flaw in the TMS Amelia (ameliabooking) WordPress booking plugin affects every version through 2.4.10 and lets any internet-connected attacker pull data straight out of the site's WordPress database, with no credentials or user interaction required. Because the plugin is broadly deployed on booking and appointment sites, every unpatched instance should be treated as an open door to customer, booking, and potentially credential-adjacent data. No vendor patch is available, so the exposure window remains open until containment measures are in place.
No vendor-released patch identified at time of analysis. Interim mitigations: deactivate or uninstall the Amelia plugin on all instances at or below 2.4.10 where it is not essential; where it must remain active, place affected sites behind a WAF or reverse proxy with SQL injection rules targeting Amelia endpoints, restrict access to booking and admin paths by IP allowlist or network segmentation, remove the plugin from internet-reachable exposure wherever possible, apply least-privilege database accounts for the WordPress instance, and monitor database and web logs for anomalous query patterns or bulk data extraction.
Threat Intelligence Overview
NVD
CVE.org
EPSS
Vulnrichment
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
SQL injection exploits the way applications construct database queries by mixing user input directly into SQL statements.
More in Wordpress Plugin
View allThe Backup Migration plugin for WordPress is vulnerable to Remote Code Execution in all versions up to, and including, 1
The Hash Form - Drag & Drop Form Builder plugin for WordPress is vulnerable to arbitrary file uploads due to missing fil
Authentication bypass in the LiteSpeed Cache WordPress plugin (versions prior to 6.5.0.1) allows unauthenticated remote
The Simple File List plugin for WordPress through version 4.2.2 contains an unauthenticated remote code execution vulner
The SureTriggers WordPress plugin through version 1.0.82 contains a privilege escalation vulnerability that allows unaut
The Ninja Forms plugin before 2.9.42.1 for WordPress allows remote attackers to conduct PHP object injection attacks via
The Business Directory Plugin - Easy Listing Directories for WordPress plugin for WordPress is vulnerable to time-based
SQL injection in the NotificationX WordPress plugin (versions up to and including 2.8.2) allows unauthenticated remote a
The POST SMTP Mailer - Email log, Delivery Failure Notifications and Best Mail SMTP for WordPress plugin for WordPress i
The MasterStudy LMS WordPress Plugin - for Online Courses and Education plugin for WordPress is vulnerable to union base
The Email Subscribers by Icegram Express plugin for WordPress is vulnerable to SQL Injection via the ‘hash’ parameter in
Remote code execution in the WP Query Console WordPress plugin (versions up to and including 1.0) by Ajit Bohra allows u
Exploit-DB