CVE-2026-39487
Blind SQL Injection in AmeliaBooking Plugin Versions
Publication date: 2026-04-08
Last updated on: 2026-04-10
Assigner: Patchstack
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| ameliabooking | amelia | to 2.1.1 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-89 | The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. Without sufficient removal or quoting of SQL syntax in user-controllable inputs, the generated SQL query can cause those inputs to be interpreted as SQL instead of ordinary user data. |
Attack-Flow Graph
AI Powered Q&A
How does this vulnerability affect compliance with common standards and regulations (like GDPR, HIPAA)?:
The SQL Injection vulnerability in the Amelia Plugin allows unauthorized access to the plugin's database, potentially leading to unauthorized data access or theft.
Such unauthorized data access can result in the exposure of personal or sensitive information, which may lead to non-compliance with data protection regulations like GDPR and HIPAA that require safeguarding personal data against unauthorized access.
Therefore, if exploited, this vulnerability could compromise compliance with these common standards and regulations by failing to protect sensitive data adequately.
How can this vulnerability be detected on my network or system? Can you suggest some commands?
This vulnerability is a Blind SQL Injection in the Amelia WordPress plugin versions up to 2.1.1. Detection typically involves testing the plugin's input fields or parameters for SQL injection flaws.
A common approach is to use automated tools or manual testing techniques to send crafted SQL payloads and observe the application's behavior or error messages.
Since this is a Blind SQL Injection, direct error messages may not be visible, so timing-based or boolean-based payloads can be used.
- Use tools like sqlmap with appropriate parameters targeting the vulnerable plugin endpoints.
- Example sqlmap command: sqlmap -u "http://targetsite.com/wp-admin/admin-ajax.php?action=amelia_ajax_action" --data="parameter=value" --technique=B --batch
- Manually test input fields by injecting payloads such as ' OR SLEEP(5)-- to check for time delays indicating Blind SQL Injection.
Additionally, checking the plugin version installed on your WordPress site can help detect vulnerability presence. Versions ≤ 2.1.1 are vulnerable.
- Command to check plugin version via WP-CLI: wp plugin get ameliabooking --field=version
Can you explain this vulnerability to me?
CVE-2026-39487 is a SQL Injection vulnerability found in the WordPress Amelia Plugin versions up to and including 2.1.1.
This vulnerability allows a malicious actor with custom developer role privileges to interact directly with the plugin's database by injecting malicious SQL commands.
It is classified under the OWASP Top 10 category A3: Injection, meaning it involves improper neutralization of special elements used in SQL commands.
How can this vulnerability impact me? :
The vulnerability can lead to unauthorized access or theft of data stored in the plugin's database.
Because it is a SQL Injection flaw, attackers could potentially manipulate or extract sensitive information from the database.
However, exploitation requires a custom developer role privilege, which limits the likelihood of attack.
Users are advised to update to version 2.1.2 or later to mitigate this risk.
What immediate steps should I take to mitigate this vulnerability?
To mitigate the SQL Injection vulnerability in the Amelia Plugin (versions up to 2.1.1), users should update the plugin to version 2.1.2 or later, where the issue has been patched.
Additionally, enabling auto-update features provided by Patchstack can help ensure rapid mitigation of this and other vulnerabilities.