WordPress Amelia plugin <= 2.2 - Sensitive Data Exposure vulnerability

published 2026-06-15 4 mo ago modified 2026-10-25 14 d ago also EUVD-2026-36992

cvss: 7.5; version 3.1, CNA
cisa kev: Not listed; not in CISA's catalog
epss: 0.3%; EPSS 0.3% chance of exploitation in 30 days, percentile 22%
public exploits: 0; none known

Unauthenticated Sensitive Data Exposure in Amelia <= 2.2 versions.

Patch / fix

fixed in 1

TMS Amelia 2.2.1

CISA SSVC

Exploitation: none
Automatable: yes
Technical impact: partial
Assessed: 4 mo ago (2026-06-16)

Exploit prediction

0.29% chance of exploitation in the next 30 days, higher than 22% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by	version	score	vector
CNA	3.1	7.5	CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

Affected products

TMS Amelia

Classification

Weakness

CWE-201 Insertion of Sensitive Information Into Sent Data

Technology feeds

WordPress rss critical rss

References

patchstack.com /database/wordpress/plugin/ameliabooking/vulnerability/wordpress-amelia-plugin-2-2-sensitive-data-exposure-vul
vdb-entry

Sources

CVE List CVE-2026-40789
NVD CVE-2026-40789

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.

CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.

Summary