HomeWordPress vulnerabilitiesSalon Booking System
Salon Booking System vulnerabilities
Salon Booking System has 37 known vulnerabilities in this database. The most recent published record is dated 21 Nov 2026.
- Known vulnerabilities
- 37
- Active installs
- 2,000+
- Latest version
- 10.31.15
- Last updated
- 7 Nov 2026
- Most recent
- 21 Nov 2026
No fixed version has been published yet, so consider disabling, removing or replacing the plugin until a safe release is available.
Find it in your WordPress dashboard under Plugins. Severity is based on the CVSS score published with the CVE where one is available.
| Vulnerability | Severity | Affected | Fix | Published |
|---|---|---|---|---|
| Broken access control CVE-2026-119607 | Medium 4.3 | Up to 10.31.16 | No fixed version yet | 1 d ago |
| Cross-site scripting (XSS) CVE-2026-124272 | High 7.1 | Up to 10.31.14 | Fixed in a later version (latest 10.31.15) | 9 d ago |
| Security weakness CVE-2026-110034 | Low 3.7 | Before 10.31.11 | Fixed in 10.31.11 | 19 Oct 2026 |
| Privilege escalation CVE-2026-110031 | High 7.2 | Before 10.31.11 | Fixed in 10.31.11 | 18 Oct 2026 |
| Broken access control CVE-2026-110032 | Medium 5.5 | Before 10.31.11 | Fixed in 10.31.11 | 18 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-110033 | Medium 6.8 | Before 10.31.11 | Fixed in 10.31.11 | 18 Oct 2026 |
| Broken access control CVE-2026-110035 | Medium 4.3 | Before 10.31.11 | Fixed in 10.31.11 | 18 Oct 2026 |
| Sensitive data exposure CVE-2026-110012 | Medium 4.3 | Before 10.31.3 | Fixed in 10.31.3 | 16 Oct 2026 |
| Authentication bypass CVE-2026-110013 | Medium 4.8 | Before 10.31.9 | Fixed in 10.31.9 | 16 Oct 2026 |
| Broken access control CVE-2026-110014 | Medium 5.3 | Before 10.31.9 | Fixed in 10.31.9 | 16 Oct 2026 |
| Cross-site request forgery (CSRF) CVE-2026-110015 | High 8.8 | Before 10.31.9 | Fixed in 10.31.9 | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-109232 | High 7.2 | Up to 10.31.9 | Fixed in a later version (latest 10.31.15) | 16 Oct 2026 |
| Cross-site scripting (XSS) CVE-2026-94668 | High 7.1 | Up to 10.31.5 | Fixed in a later version (latest 10.31.15) | 9 Oct 2026 |
| Privilege escalation CVE-2026-105070 | High 8.8 | Up to 10.31.7 | Fixed in a later version (latest 10.31.15) | 6 Oct 2026 |
| Broken access control CVE-2026-81793 | Medium 6.5 | Up to 10.31.9 | Fixed in a later version (latest 10.31.15) | 10 Sep 2026 |
| Broken access control CVE-2026-17020 | Medium 4.3 | Up to 10.31.0 | Fixed in a later version (latest 10.31.15) | 10 Aug 2026 |
| Broken access control CVE-2026-17021 | Medium 5.3 | Before 10.30.34 | Fixed in 10.30.34 | 10 Aug 2026 |
| Sensitive data exposure CVE-2026-17022 | High 7.5 | Before 10.30.34 | Fixed in 10.30.34 | 10 Aug 2026 |
| Broken access control CVE-2026-17023 | Medium 4.8 | Up to 10.30.33 | Fixed in a later version (latest 10.31.15) | 10 Aug 2026 |
| Cross-site request forgery (CSRF) CVE-2026-15070 | High 8.8 | Up to 10.30.32 | Fixed in a later version (latest 10.31.15) | 10 Jul 2026 |
| Security weakness CVE-2026-11887 | Medium 4.3 | Before 10.30.20 | Fixed in 10.30.20 | 1 Jul 2026 |
| Arbitrary file read CVE-2026-6320 | High 7.5 | Up to 10.30.25 | Fixed in a later version (latest 10.31.15) | 2 May 2026 |
| Broken access control CVE-2025-8492 | Medium 5.3 | Up to 10.22 | Fixed in a later version (latest 10.31.15) | 11 Sep 2025 |
| Cross-site scripting (XSS) CVE-2024-9882 | Medium 4.8 | Before 1.9.4 | Fixed in 1.9.4 | 15 May 2025 |
| Broken access control CVE-2025-32220 | Medium 5.4 | Up to 10.31.9 | Fixed in a later version (latest 10.31.15) | 4 Apr 2025 |
| Remote code execution CVE-2024-3229 | Critical 9.8 | Before 10.3 | Fixed in 10.3 | 19 Jun 2024 |
| Broken access control CVE-2024-4468 | Medium 4.3 | Before 10.0 | Fixed in 10.0 | 8 Jun 2024 |
| Remote code execution CVE-2024-4442 | Critical 9.1 | Before 10.0 | Fixed in 10.0 | 21 May 2024 |
| Cross-site request forgery (CSRF) CVE-2024-2429 | Medium 4.3 | Before 9.6.6 | Fixed in 9.6.6 | 26 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-2439 | Medium 4.8 | Before 9.6.6 | Fixed in 9.6.6 | 26 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-2603 | Medium 6.3 | Before 9.6.6 | Fixed in 9.6.6 | 26 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-2101 | Medium 5.7 | Before 9.6.3 | Fixed in 9.6.3 | 17 Apr 2024 |
| Cross-site scripting (XSS) CVE-2024-2102 | Medium 4.7 | Before 9.6.3 | Fixed in 9.6.3 | 17 Apr 2024 |
| Cross-site request forgery (CSRF) CVE-2023-3427 | Medium 5.4 | Up to 8.4.6 | Fixed in a later version (latest 10.31.15) | 28 Jun 2023 |
| Broken access control CVE-2022-0919 | Medium 5.3 | Before 7.6.3 | Fixed in 7.6.3 | 11 Apr 2022 |
| Broken access control CVE-2022-0920 | High 7.5 | Before 7.6.3 | Fixed in 7.6.3 | 11 Apr 2022 |
| Cross-site scripting (XSS) CVE-2021-24429 | Medium 6.1 | Before 6.3.1 | Fixed in 6.3.1 | 12 Jul 2021 |
Read the published descriptions
- CVE-2026-119607, 21 Nov 2026
- The Salon Booking System - Appointment Booking for Salons, Barbershops & Spas plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 10.31.16. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for authenticated attackers, with subscriber-level access and above, to overwrite arbitrary users' user meta fields, including the _sln_phone and _sln_sms_prefix meta of administrator accounts, and create bookings attributed to arbitrary users. This is exploitable on default installations because reCAPTCHA is disabled by default, causing the booking endpoint's permission check to return true for any authenticated user without a meaningful authorization gate. CVE record
- CVE-2026-124272, 13 Nov 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dimitri Grassi Salon booking system salon-booking-system allows Reflected XSS.This issue affects Salon booking system: from n/a through 10.31.14. CVE record
- CVE-2026-110034, 19 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.11 does not enforce a minimum of zero when subtracting a fixed-amount discount from a booking's total, allowing an unauthenticated visitor who knows a valid discount code to create a confirmed booking stored with a negative total. CVE record
- CVE-2026-110031, 18 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.11 does not prevent users holding its custom salon staff role from assigning arbitrary capabilities to other accounts when editing a customer, allowing them to escalate any account to administrator and take over the site. CVE record
- CVE-2026-110032, 18 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.11 does not restrict which user account its salon staff roles may edit through the customers management screen, allowing users with the Salon Staff or Salon Worker role to reset any other user's role, including administrators, to a customer and to overwrite arbitrary profile fields on any account, leading to loss of administrative access and potential site lockout. CVE record
- CVE-2026-110033, 18 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.11 does not validate a user-supplied image URL before fetching it server-side and writing the response to a publicly accessible location under an attacker-chosen filename, allowing users with the Salon Staff role or higher to force the server to read internal-only resources and disclose them, and to store a malicious SVG that runs arbitrary scripts in the site's origin for anyone who opens it. CVE record
- CVE-2026-110035, 18 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.11 does not restrict one of its REST API endpoints to salon staff, allowing any authenticated user, such as a subscriber, to retrieve every discount coupon configured on the site, including coupons the administrator has chosen to hide from customers, together with their amounts, validity dates and usage limits. CVE record
- CVE-2026-110012, 16 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.3 does not restrict several of its booking REST API routes to users with the appropriate capability, allowing any authenticated user such as a subscriber to read every customer's booking records, including their personal data. CVE record
- CVE-2026-110013, 16 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.9 does not generate its booking-API access tokens from a secure random source, instead deriving them from a value hardcoded in the Salon Booking System WordPress plugin before 10.31.9 and the second at which a token was issued. An attacker able to constrain when a staff or administrator token was issued can compute a valid token and access the booking API as that user, including an administrator. CVE record
- CVE-2026-110014, 16 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.9 does not properly check authorization before creating a booking and trusts a caller-supplied user identifier and booking status, allowing unauthenticated attackers to create bookings attributed to arbitrary users, overwrite those users' stored contact details, and mark bookings as paid or confirmed without any payment. CVE record
- CVE-2026-110015, 16 Oct 2026
- The Salon Booking System WordPress plugin before 10.31.9 does not correctly verify the authenticity of REST API requests and discards WordPress core's nonce check for cookie-authenticated sessions across the whole REST API, allowing unauthenticated attackers who trick a logged-in administrator into clicking a crafted link to forge requests in that administrator's browser, up to creating a new administrator account. CVE record
- CVE-2026-109232, 16 Oct 2026
- The Salon Booking System - Appointment Booking for Salons, Barbershops & Spas plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'sln[<checkout-field-key>]' parameter in all versions up to, and including, 10.31.9 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. Exploitation requires that the site administrator has configured at least one custom checkout field of type Html or File, which is a standard documented plugin feature. CVE record
- CVE-2026-94668, 9 Oct 2026
- Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in Dimitri Grassi Salon booking system salon-booking-system allows Reflected XSS.This issue affects Salon booking system: from n/a through 10.31.5. CVE record
- CVE-2026-105070, 6 Oct 2026
- Unauthenticated Privilege Escalation in Salon booking system <= 10.31.7 versions. CVE record
- CVE-2026-81793, 10 Sep 2026
- Missing Authorization vulnerability in Dimitri Grassi Salon booking system salon-booking-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Salon booking system: from n/a through 10.31.9. CVE record
- CVE-2026-17020, 10 Aug 2026
- The Salon Booking System WordPress plugin through 10.31.0 does not verify that a requested booking belongs to the caller on one of its REST API endpoints, requiring only a basic read capability, allowing any authenticated user (including a Subscriber or self-registered customer account) to disclose any customer's booking personal data such as name, email, phone number, address and private notes by enumerating booking identifiers. CVE record
- CVE-2026-17021, 10 Aug 2026
- The Salon Booking System WordPress plugin before 10.30.34 does not properly restrict access to some of its booking-modification AJAX actions and does not verify ownership of the targeted booking, allowing unauthenticated users to tamper with the stored total of arbitrary bookings. CVE record
- CVE-2026-17022, 10 Aug 2026
- The Salon Booking System WordPress plugin before 10.30.34 does not properly validate a booking's ownership token before loading it in its booking-wizard confirmation steps, allowing unauthenticated attackers to disclose other customers' booking records, including personal information, by supplying a sequential booking identifier. CVE record
- CVE-2026-17023, 10 Aug 2026
- The Salon Booking System WordPress plugin through 10.30.33 does not perform any capability check or validate an OAuth state value on its Google Calendar authorization callback, which is also hooked for unauthenticated users, allowing an unauthenticated attacker to overwrite the site's stored Google Calendar connection tokens with attacker-controlled ones and hijack the integration. Exploitation requires the site to have configured its own Google OAuth client for the calendar feature. CVE record
- CVE-2026-15070, 10 Jul 2026
- The Salon Booking System - Free Version plugin for WordPress is vulnerable to Cross-Site Request Forgery in all versions up to, and including, 10.30.32. This is due to missing or incorrect nonce validation on the setCustomText function. This makes it possible for unauthenticated attackers to inject arbitrary PHP code into the web-accessible translate-constants.php file within the plugin directory, enabling remote code execution on the server via a forged request granted they can trick a site administrator into performing an action such as clicking on a link. sanitize_text_field() is applied to the POST 'value' parameter but does not neutralize the characters - single quotes, parentheses, semicolons, $, and [] - required to break out of the PHP string literal into which the value is interpolated before being written to disk via file_put_contents(). CVE record
- CVE-2026-11887, 1 Jul 2026
- The Salon Booking System WordPress plugin before 10.30.20 does not have proper authorisation checks on one of its AJAX actions, allowing any authenticated user, such as a subscriber, to modify a Salon Booking System WordPress plugin before 10.30.20 setting and bypass the manual approval of new bookings. CVE record
- CVE-2026-6320, 2 May 2026
- The Salon Booking System - Free Version plugin for WordPress is vulnerable to Arbitrary File Read in versions up to, and including, 10.30.25. This is due to the public booking flow accepting attacker-controlled file-field values and later using those stored values as trusted paths for email attachments. This makes it possible for unauthenticated attackers to read arbitrary local files and exfiltrate them via booking confirmation email attachments. CVE record
- CVE-2025-8492, 11 Sep 2025
- The Salon Booking System, Appointment Scheduling for Salons, Spas & Small Businesses plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the ajax function in all versions up to, and including, 10.22. This makes it possible for unauthenticated attackers to execute AJAX actions, including limited file uploads. CVE record
- CVE-2024-9882, 15 May 2025
- The Salon Booking System, Appointment Scheduling for Salons, Spas & Small Businesses WordPress plugin before 1.9.4 does not sanitise and escape some of its settings, which could allow high privilege users such as admin to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup). CVE record
- CVE-2025-32220, 4 Apr 2025
- Missing Authorization vulnerability in Dimitri Grassi Salon booking system salon-booking-system allows Exploiting Incorrectly Configured Access Control Security Levels.This issue affects Salon booking system: from n/a through 10.31.9. CVE record
- CVE-2024-3229, 19 Jun 2024
- The Salon booking system plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the SLN_Action_Ajax_ImportAssistants function along with missing authorization checks in all versions up to, and including, 10.2. This makes it possible for unauthenticated attackers to upload arbitrary files on the affected site's server which may make remote code execution possible. CVE record
- CVE-2024-4468, 8 Jun 2024
- The Salon booking system plugin for WordPress is vulnerable to unauthorized access and modification of data due to a missing capability check on several functions hooked into admin_init in all versions up to, and including, 9.9. This makes it possible for authenticated attackers with subscriber access or higher to modify plugin settings and view discount codes intended for other users. CVE record
- CVE-2024-4442, 21 May 2024
- The Salon booking system plugin for WordPress is vulnerable to arbitrary file deletion in all versions up to, and including, 9.8. This is due to the plugin not properly validating the path of an uploaded file prior to deleting it. This makes it possible for unauthenticated attackers to delete arbitrary files, including the wp-config.php file, which can make site takeover and remote code execution possible. This was partially patched in 9.9, and sufficiently patched in 10.0. CVE-2024-37231 appears to be a duplicate of this issue. CVE record
- CVE-2024-2429, 26 Apr 2024
- The Salon booking system WordPress plugin through 9.6.5 does not have CSRF check in place when updating its settings, which could allow attackers to make a logged in admin change them via a CSRF attack CVE record
- CVE-2024-2439, 26 Apr 2024
- The Salon booking system WordPress plugin through 9.6.5 does not sanitise and escape some of its settings, which could allow high privilege users such as Editor to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-2603, 26 Apr 2024
- The Salon booking system WordPress plugin through 9.6.5 does not sanitise and escape some of its settings, which could allow high privilege users such as admin (or editor depending on Salon booking system WordPress plugin through 9.6.5 configuration) to perform Stored Cross-Site Scripting attacks even when the unfiltered_html capability is disallowed (for example in multisite setup) CVE record
- CVE-2024-2101, 17 Apr 2024
- The Salon booking system WordPress plugin before 9.6.3 does not properly sanitize and escape the 'Mobile Phone' field when booking an appointment, allowing customers to conduct Stored Cross-Site Scripting attacks. The payload gets triggered when an admin visits the 'Customers' page and the malicious script is executed in the admin context. CVE record
- CVE-2024-2102, 17 Apr 2024
- The Salon booking system WordPress plugin before 9.6.3 does not properly sanitize and escape the 'Mobile Phone' field and 'sms_prefix' parameter when booking an appointment, allowing customers to conduct Stored Cross-Site Scripting attacks. The payload gets triggered when an admin visits the 'Bookings' page and the malicious script is executed in the admin context. CVE record
- CVE-2023-3427, 28 Jun 2023
- The Salon Booking System plugin for WordPress is vulnerable to Cross-Site Request Forgery in versions up to, and including, 8.4.6. This is due to missing or incorrect nonce validation on the 'save_customer' function. This makes it possible for unauthenticated attackers to change the admin role to customer or change the user meta to arbitrary values via a forged request, granted they can trick a site administrator into performing an action such as clicking on a link. CVE record
- CVE-2022-0919, 11 Apr 2022
- The Salon booking system Free and pro WordPress plugins before 7.6.3 do not have proper authorisation when searching bookings, allowing any unauthenticated users to search other's booking, as well as retrieve sensitive information about the bookings, such as the full name, email and phone number of the person who booked it. CVE record
- CVE-2022-0920, 11 Apr 2022
- The Salon booking system Free and Pro WordPress plugins before 7.6.3 do not have proper authorisation in some of its endpoints, which could allow customers to access all bookings and other customer's data CVE record
- CVE-2021-24429, 12 Jul 2021
- The Salon booking system WordPress plugin before 6.3.1 does not properly sanitise and escape the First Name field when booking an appointment, allowing low privilege users such as subscriber to set JavaScript in them, leading to a Stored Cross-Site Scripting (XSS) vulnerability. The Payload will then be triggered when an admin visits the "Calendar" page and the malicious script is executed in the admin context. CVE record
What to do if you run Salon Booking System
If you run Salon Booking System, open WordPress and check the installed version in Plugins. Compare it with the affected versions in the vulnerability record. If a fixed version is available, take a current backup and update to that version or the latest supported release.
If no fixed version exists, consider disabling and removing the plugin or replacing it with a maintained alternative. After dealing with the affected software, check administrator users, unexpected file changes, redirects, unfamiliar pages and security logs for signs that the site may already have been altered.
Email me about new Salon Booking System vulnerabilities
Free. We email you when a new vulnerability is published for Salon Booking System, usually within minutes. Confirm by email; unsubscribe any time.
Focus on your business. We’ll take care of your website.
From everyday updates to ongoing care, we keep your website working.