Answer in brief
CVE-2026-119607 records a Medium severity (CVSS 4.3) vulnerability in Salon Booking System <= 10.31.16 - Missing Authorization to Authenticated (Subscriber+) Arbitrary User Meta Overwrite via 'customer_id' Parameter. The current sources do not mark it as known exploited. The current feed maps wordpresschef/Salon Booking System – Appointment Booking for Salons, Barbershops & Spas (generic). Check affected ranges and fixed versions before updating.
Analysis pending evidence review
HOL Guard separates source facts from reviewed analysis. See the methodology.
CVSS is 4.3. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.
Analysis status
Analysis pending evidence review
Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.
The current feed maps wordpresschef/Salon Booking System – Appointment Booking for Salons, Barbershops & Spas (generic). Check affected ranges and fixed versions before updating.
| Package | Affected range | Fixed version |
|---|---|---|
| wordpresschef/Salon Booking System – Appointment Booking for Salons, Barbershops & Spasgeneric | >=0 <=10.31.16 | Not reported |
Published upstream
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordSource modified
Nov 21, 2026
Evidence: source:cvelist:source_dates:source-dates:recordFirst seen by HOL
Nov 21, 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.
Quoted source text, attributed separately from HOL analysis.