Skip to main content

Amelia Booking Calendar CVE-2026-103915

| EUVDEUVD-2026-114671 MEDIUM
Information Exposure (CWE-200)
2026-10-31 Wordfence GHSA-v33c-8q9v-p4jw
5.3
CVSS 3.1 · NVD
View

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK

2 techniques across 2 tactics: Collection, Discovery

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Impact

This is a genuine but moderate-priority exposure, not an emergency. The CVSS vector (AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N = 5.3) is internally consistent with the description: a remote, unauthenticated, low-complexity request against a network-facing WordPress endpoint, with impact limited to confidentiality of a bounded data set (C:L, no integrity or availability impact). The signals do not conflict with each other. KEV status is NOT listed, so there is no confirmed active exploitation. No EPSS score was provided in the input, so exploitation probability cannot be quantified from the available data - this is a gap, not a low score. No verified working exploit code is present; the references are the Wordfence advisory and WordPress trac source-code lines pinpointing the flaw, which disclose the mechanism but are not a packaged PoC. The vendor priority label is 'this_month', which aligns with a real-but-not-critical information-disclosure issue: the ease of exploitation (unauthenticated, default behavior) raises urgency, while the limited, non-destructive impact (staff PII and internal notes, no code execution or data modification) caps it. Treat as a scheduled-patch item rather than a drop-everything incident, noting that mass automated scraping of exposed PII is plausible given the trivial trigger.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.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 – Oct 31, 2026

Unauthenticated information disclosure in the Amelia booking plugin for WordPress (all versions through 2.4.12) lets remote attackers harvest staff personally identifiable information - full name, email address, phone number, gender and timezone - along with administrator-authored internal notes for every published event, by supplying a crafted 'page' parameter that causes the raw providers array to be serialized into the JSON response. With a CVSS score of 5.3 (AV:N/AC:L/PR:N/UI:N, confidentiality-only at C:L), the issue is a genuine but moderate-priority data leakage exposure rather than an emergency, and the available intelligence indicates no public exploit code and no confirmed active exploitation at time of analysis.

RemediationAI

Because the affected range is stated as every version up to and including 2.4.12, the remediation is to move the Amelia plugin to a release later than 2.4.12 as documented in the Wordfence advisory (https://www.wordfence.com/threat-intel/vulnerabilities/id/25571e59-c966-4d30-9453-42b63778b9a0?source=cve); the supplied intelligence does not name the exact patched version, so confirm the fixed release in that advisory before upgrading. The provided references are source links to the vulnerable 2.4.11 tag rather than to a fix, and no workaround or compensating control is documented in the available sources, so there is no vendor-endorsed configuration change to cite - the exposure is only fully closed by running a patched build of the plugin.

Affected VersionsENISA

Booking for Appointments and Events Calendar – Amelia 0 ≤2.4.12

Affected Packages

euvd booking_for_appointments_and_events_calendar_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 is a commercial WordPress booking and events plugin from Melograno that serves event and appointment data through PHP controller and command classes; the supplied references point at GetEventsController.php and GetEventsCommandHandler.php within the 2.4.11 plugin tag, plus the plugin's main bootstrap file (ameliabooking.php). The root cause is CWE-200, Exposure of Sensitive Information to an Unauthorized Actor: the event-listing response carries the full provider (staff) record array and administrator-authored internal notes, and that raw array is never stripped or reduced to a public-safe projection before the payload is serialized to JSON. Per the CVSS vector the reachable path requires no authentication (PR:N) and no user interaction, so a request carrying a manipulated 'page' parameter is enough to return the leaked fields for every provider and every published event; impact is confidentiality-only (C:L) with no integrity or availability effect. The specific code locations for the trigger are identified by the referenced source lines rather than spelled out in the advisory text.

Know when Booking For Appointments And Events Calendar 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

No credit card · 7-day full trial

Severity by source

Vendor (Wordfence) PRIMARY MEDIUM
NVD 5.3 MEDIUM
AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N

Primary rating from Vendor (Wordfence).

CVSS VectorNVD

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

DescriptionNVD

The Booking for Appointments and Events Calendar - Amelia plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 2.4.12 via the 'page' parameter. This makes it possible for unauthenticated attackers to extract staff personally identifiable information - including full name, email address, phone number, gender, and timezone - as well as administrator-authored internal notes for every published event, all serialized into the JSON response because the raw providers array is never stripped before output.

Threat Intelligence Overview

EPSS Score
0.3%
Top 83% exploitable
Social Media
1
Sightings
Data Quality
4 sources
Confidence: Medium

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 MEDIUM
CISA KEV No
Public POC No
EPSS 0.3%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.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· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
Yes
Human Impact· derived
Medium

Priority Score

26
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +26
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

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

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy