CVE-2026-39487: ameliabooking Amelia Blind SQL Injection

CVE-2026-39487 · Severity: high · CVSS 7.6 · Published 2026-04-08

Amelia is a popular WordPress plugin used for managing appointments and event bookings. A security vulnerability in this plugin could allow an attacker with administrative or high-level privileges to interact directly with the website's database. This could lead to the unauthorized extraction of sensitive information, such as customer data or site configuration details.

Quick answers

Is CVE-2026-39487 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-39487 being exploited in the wild.
How severe is CVE-2026-39487?
High severity, with a CVSS score of 7.6, published 8 April 2026.
Which products and versions are affected?
ameliabooking Amelia <= 2.1.1.
Is there a fix for CVE-2026-39487?
A patch was published on 2026-03-25: Patch released in version 2.1.2 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-39487 attacked?
It is attacked over the network, in a software library.
Am I affected by CVE-2026-39487?
Check whether anything you run is named in the advisory. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A Blind SQL Injection vulnerability exists in the ameliabooking (Amelia) plugin for WordPress through version 2.1.1. The flaw stems from improper neutralization of special elements used in SQL commands (CWE-89). An attacker with high privileges (such as a custom role or administrator) can exploit this over the network without user interaction to execute arbitrary SQL queries. This can be used to exfiltrate sensitive data from the database. The issue is addressed in version 2.1.2.

Affected products

  • ameliabooking Amelia <= 2.1.1

Timeline

  • 2026-02-23: other: Vulnerability reported by researcher daroo
  • 2026-03-25: disclosed: Initial disclosure by Patchstack
  • 2026-04-08: advisory: CVE published to NVD
  • 2026-03-25: patched: Patch released in version 2.1.2

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.