Skip to main content
VulnerabilityPublished

CVE-2026-119607: Salon Booking System (WordPress plugin) · Missing Authorization

Affects Salon Booking System (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium.

Data as of 21 Nov 2026, 05:44 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.14.3
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 21 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 20 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
wordpresschefSalon Booking System – Appointment Booking for Salons, Barbershops & SpasAffected
  • <=10.31.16
Fixed in–

AI-suggested

Users should verify if a vendor advisory or update has been released to address this issue. Until a fix is available, administrators should consider restricting subscriber-level access or enabling reCAPTCHA to enforce stricter authorization checks on the booking endpoint. Monitor vendor communications for official remediation guidance.

Description

The Salon Booking System plugin for WordPress up to version 10.31.16 contains an authorization bypass vulnerability. Authenticated users with subscriber-level access or higher can overwrite arbitrary user meta fields, including those of administrator accounts, and create bookings attributed to any user. This occurs because the plugin does not properly verify user authorization, and the default configuration disables reCAPTCHA, allowing the booking endpoint's permission check to succeed for any authenticated user.

References

Community reviews

Loading reviews…