CVE-2026-6286 Cross-site scripting in Booking for Appointments and Events Calendar – Amelia
Unauthenticated attackers can inject malicious scripts via customer name fields that execute in the admin calendar view, potentially leading to account takeover.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-6286?
CVE-2026-6286 is a high-severity cross-site scripting vulnerability in melograno Booking for Appointments and Events Calendar – Amelia, published on 28 Aug 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
The Booking for Appointments and Events Calendar – Amelia plugin for WordPress is vulnerable to Stored Cross-Site Scripting via customer name fields in versions up to and including 2.2. This is due to an authentication bypass where the AddBookingCommand explicitly skips nonce verification (Command.php line 186), allowing unauthenticated users to submit booking data. While the plugin applies sanitize_text_field() to customer firstName and lastName fields (BookingApplicationService.php lines 302-308), this function only removes HTML tags and preserves special characters including double quotes. The vulnerability manifests in the administrative Calendar view where a FullCalendar eventContent callback interpolates customer names directly into JavaScript template literals (redesign/dist/index.js line 199) and renders them via innerHTML without proper HTML entity encoding. Because double quotes are preserved, an attacker can inject payloads like '" onmouseover="alert(document.cookie)"' to break out of the title attribute and inject malicious event handlers. This makes it possible for unauthenticated attackers to inject arbitrary web scripts that will execute when an administrator accesses the Calendar page and hovers over the malicious appointment.
Weakness: CWE-79
Which versions are affected by CVE-2026-6286?
How do I fix CVE-2026-6286?
No fix has been published for CVE-2026-6286 yet. Limit exposure of the affected software until one is available.
Escape output for the context it lands in and set a strict Content Security Policy. Upgrading the affected component is the real fix. More about Cross-site scripting.
Is CVE-2026-6286 being exploited?
There is no known exploitation of CVE-2026-6286 in the wild and no public exploit code.
Sources
Also known as GHSA-6v29-784x-wf4r.