What is the CVSS score of CVE-2026-40789?

CVE-2026-40789 has a CVSS 3.1 base score of 7.5 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N. EPSS exploitation probability: 0.3%.

How to fix or mitigate CVE-2026-40789?

Within 24 hours: Identify all WordPress instances running Amelia plugin v2.2 or earlier; document business function, data sensitivity, and affected customer base for each. Within 7 days: Implement Web Application Firewall (WAF) rules to restrict plugin access; apply network-level controls limiting access to known administrative IP ranges; assess feasibility of disabling plugin if non-critical. Within 30 days: Execute primary remediation (disable, replace, or apply patch if released); deploy monitoring for exploitation attempts; conduct data access audit to confirm whether unauthorized access occurred.

Amelia CVE-2026-40789

Q: Which versions of Amelia are affected by CVE-2026-40789?

The Amelia Booking WordPress plugin (v2.2 and earlier) contains an unauthenticated vulnerability enabling remote access to sensitive customer and business data.

EUVD-2026-36992 HIGH

Insertion of Sensitive Information Into Sent Data (CWE-201)

2026-06-15 Patchstack

GHSA-cfv8-838c-fm27

WordPress Information Disclosure Amelia Wordpress Plugin Tms

7.5

CVSS 3.1 · Vendor: Patchstack

View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

Access

Identify WordPress site running Amelia <=2.2
Exploit

Send unauthenticated request to vulnerable endpoint
Execution

Receive sensitive booking data in response
Impact

Harvest customer PII at scale

Vulnerability Assessment

Weakness	CWE CWE-201 OWASP Top 10:2025 A01:2025 - Broken Access Control ASVS 5.0 V14 - Data Protection Outbound data filtering
Exploitation Conditions	No special conditions - remote unauthenticated exploitation against default configurations of the Amelia WordPress plugin at version 2.2 or earlier, consistent with AV:N/AC:L/PR:N/UI:N. The only limiting factors are that the target WordPress site must have the Amelia plugin installed and active, must be running version <=2.2, and the vulnerable endpoint must be reachable from the attacker's network (i.e. not behind an IP allowlist or WAF rule blocking the affected route). No user interaction, no administrator session, and no non-default plugin configuration is required.
Impact	The CVSS vector AV:N/AC:L/PR:N/UI:N/C:H/I:N/A:N is internally consistent with an information-disclosure flaw reachable over the network with no authentication or interaction - a textbook 'easy to exploit, confidentiality-only' profile that justifies the 7.5 High rating. EPSS and CISA KEV status are not provided in the input, so likelihood of mass exploitation cannot be quantitatively scored; no public exploit identified at time of analysis. Real-world priority is meaningful: Amelia is a popular WordPress plugin and PR:N+AC:L information-disclosure bugs against booking systems are routinely scraped, so defenders running Amelia should treat this as a near-term remediation item rather than a theoretical issue, while acknowledging that without a CWE-specific endpoint detail in the public advisory the exact data exposed is unconfirmed.
Exploit ScenarioDerived	An unauthenticated attacker sends crafted HTTP requests to Amelia's public REST or admin-ajax endpoints on a target WordPress site and receives back sensitive booking data - customer names, contact details, appointment schedules, or internal identifiers - that should require authentication or capability checks. With AC:L and PR:N this can be automated at scale by scanning WordPress sites running the plugin and harvesting the exposed records; no public exploit identified at time of analysis, but the low complexity makes weaponization straightforward once the vulnerable endpoint is reverse-engineered from the patch.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).

No patch listed yet 0.3% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Jun 15, 2026

Unauthenticated sensitive data exposure in the Amelia (Amelia Booking) WordPress plugin versions 2.2 and earlier allows remote attackers to retrieve protected information without credentials, per a Patchstack advisory. With a CVSS 7.5 (AV:N/AC:L/PR:N/UI:N) and CWE-201 classification, the flaw is network-reachable and trivially triggerable, though no public exploit identified at time of analysis and no CISA KEV listing.

RemediationAI

Upgrade the Amelia plugin to a version newer than 2.2 once the vendor publishes a fixed release; the Patchstack advisory at https://patchstack.com/database/wordpress/plugin/ameliabooking/vulnerability/wordpress-amelia-plugin-2-2-sensitive-data-exposure-vulnerability is the canonical reference and will list the patched version. Patch available per vendor advisory; exact fix version is not stated in the provided input, so administrators should confirm the current Amelia release on the WordPress.org plugin page before upgrading. Until patched, compensating controls include enabling Patchstack or a WAF virtual patch for this CVE, restricting access to the Amelia REST/AJAX endpoints (wp-admin/admin-ajax.php actions and /wp-json/amelia/* routes) via IP allowlisting or authenticated-only access at the web server (with the trade-off that public booking forms will break for end users), and temporarily deactivating the plugin on sites where appointment booking is not actively used.

Affected VersionsENISA

Amelia n/a ≤2.2

Affected Packages

euvd amelia no fix

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

Amelia (also known as Amelia Booking, vendor TMS / cpe:2.3:a:tms:amelia) is a widely deployed WordPress appointment-booking plugin that exposes REST/AJAX endpoints to handle bookings, customer records, employees, services, and payment metadata. CWE-201 (Insertion of Sensitive Information Into Sent Data) indicates that one or more of these endpoints, or related response payloads, returns data that should be access-controlled - typically because an authorization check is missing, an internal field is leaked into a public response, or a debug/listing endpoint can be queried without a valid nonce or capability check. Because the plugin runs inside WordPress as a privileged component handling PII (names, emails, phone numbers, appointment details, and potentially payment references), any over-broad response from its endpoints translates directly into customer-data leakage.

Know when Amelia 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

Continue with Google Continue with GitHub

No credit card · 7-day full trial

Severity by source

Vendor (Patchstack) PRIMARY 7.5 HIGH

AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

vuln.today AI 7.5 HIGH

Unauthenticated network-reachable WordPress plugin endpoint leaks sensitive data with no interaction; confidentiality-only impact, so I:N and A:N.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N

4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (Patchstack).

CVSS VectorVendor: Patchstack

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

None

Availability

None

DescriptionCVE.org

Unauthenticated Sensitive Data Exposure in Amelia <= 2.2 versions.

Executive ViewAI

Why It Matters

The Amelia Booking WordPress plugin (v2.2 and earlier) contains an unauthenticated vulnerability enabling remote access to sensitive customer and business data. While no public exploit code currently exists, the flaw is trivially exploitable due to its network accessibility and zero authentication requirements. Organizations using this plugin must immediately identify affected instances and implement mitigations to prevent data exposure.

Business Impact: High

Compensating Controls

No vendor-released patch identified at time of analysis. Interim mitigations: (1) Deploy WAF with rules blocking suspicious requests to Amelia endpoints; (2) Restrict network access to plugin directories and administrative functions to known internal IP ranges; (3) Disable the plugin if booking functionality is non-critical; (4) Implement WordPress security hardening (disable directory listing, enforce strong authentication, enable logging); (5) Establish monitoring and alerting for unusual database access patterns and data exports; (6) Classify and secure sensitive data within Amelia databases (customer PII, payment information).

Threat Intelligence Overview

EPSS Score

0.3%

Top 79% exploitable

Data Quality

6 sources

Confidence: High

EUVD

NVD

CVE.org

EPSS

Vulnrichment

VulDB

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.

SignalValue

Severity HIGH

CISA KEV No

Public POC No

EPSS 0.3%

Patch available No

Active threat No

Deciding rule

HIGH severity (CVSS 7.0-8.9)

What every action level means

Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.

Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.

This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.

This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.

Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision

Scheduled

Exploitation

None

System Exposure· derived

Open

Automatable

Yes

Human Impact

High

Technical Impact

Partial

Priority Score

Low Medium High Critical

KEV: 0

EPSS: 0

CVSS: +38

PoC: 0

Weaponized: 0

Threat intel: 0

Gov advisory: 0

Attack Technique

Information Disclosure MEDIUM

Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.