CVE-2026-6286 HIGH

CVE-2026-6286: Booking for Appointments and Events Calendar <= 2.2 - Unauthenticated Stored Cross-Site Scripting via Customer Name Fields in Booking Submission

Vendor Melograno
Product Booking for Appointments and Events Calendar – Amelia
Weakness CWE-79 · XSS
Published August 28, 2026
Last update August 28, 2026

CVSS base score

7.2/10
Attack vector Network
Attack complexity Low
Privileges required None
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

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

What the vulnerability does

01Description

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.

Explanation of Vulnerability in Simple Terms

02Summary

Amelia versions 2.2 and earlier contain a cross-site scripting (XSS) vulnerability that allows attackers to inject malicious scripts affecting multiple users. The vulnerability requires no authentication or user interaction beyond visiting a compromised page. An attacker can inject code that executes in visitors' browsers, potentially stealing session data or redirecting users to malicious sites.

What an attacker can do

03Attacker Capabilities

Inject malicious JavaScript that executes in other users' browsers when they visit the site.

Potential impact on your site

04Site Impact

Visitors' browsers can be compromised; session tokens, credentials, or personal data may be stolen or modified.

Conditions required to exploit

05Prerequisites

Network access to the site; no authentication or user interaction required.

Key dates

06Disclosure timeline

August 28, 2026 CVE published

Related vulnerabilities

08Related CVE