CVE-2026-1083
Stored XSS in Appointment Hour Booking Plugin Affects Multisite
Publication date: 2026-01-28
Last updated on: 2026-01-28
Assigner: Wordfence
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| appointment_hour_booking | booking_calendar | to 1.5.60 (inc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-79 | The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users. |
Attack-Flow Graph
AI Powered Q&A
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, ensure that you update the Appointment Hour Booking – Booking Calendar plugin to a version later than 1.5.60 where the issue is fixed. Additionally, restrict administrator-level access to trusted users only, and consider enabling unfiltered_html if possible, or review multi-site installation configurations to reduce exposure.
Can you explain this vulnerability to me?
This vulnerability is a Stored Cross-Site Scripting (XSS) issue in the Appointment Hour Booking – Booking Calendar plugin for WordPress. It occurs because the plugin does not properly sanitize or escape input in the 'Min length/characters' and 'Max length/characters' form field configuration parameters. Authenticated users with administrator-level access or higher can inject malicious scripts that will execute when other users access the form builder interface. This affects multi-site installations and installations where the unfiltered_html setting is disabled.
How can this vulnerability impact me? :
An attacker with administrator-level access can inject malicious scripts into the plugin's form builder interface. These scripts execute when users access the interface, potentially leading to unauthorized actions, data theft, or session hijacking. Since the vulnerability requires high privileges and affects multi-site or restricted HTML installations, the impact is limited but can compromise the integrity and security of the affected WordPress sites.