CVE-2026-110032 json
Salon Booking System < 10.31.11 - Salon Staff+ Administrator Role Demotion via Customer Editor
published 22d ago modified 21d ago also EUVD-2026-103393
- cvss
- 5.5
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.2%
- EPSS 0.2% chance of exploitation in 30 days, percentile 12%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- Unknown Salon Booking System 10.31.11
Is CVE-2026-110032 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 22d ago
Exploit prediction
0.22% chance of exploitation in the next 30 days, higher than 12% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- wpscan.com https://wpscan.com/vulnerability/07310082-5ccc-4703-9344-2bd6e823b245/ referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CISA ADP | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L |
| CNA | 3.1 | 5.5 | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:H/A:L |
Affected products
- Unknown Salon Booking System
Classification
- Weakness
-
- CWE-863 Incorrect Authorization
- Technology feeds
References
-
wpscan.com
/vulnerability/07310082-5ccc-4703-9344-2bd6e823b245/
exploit, vdb-entry, technical-description
Sources
- CVE List CVE-2026-110032
- NVD CVE-2026-110032
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.