Salon Booking System Flaw: Update to 10.31.11

By Bug Circuit Security Team
Salon Booking System Flaw: Update to 10.31.11

Is your own website affected? Check it free in 2 minutes.

Passive outside check only. Nothing is attacked, no signup.

If your WordPress site runs Salon Booking System older than version 10.31.11, update the plugin now: a logged-in user with the plugin's salon staff role could turn any account into an administrator and take over the site.

This post is for owners of salons, spas, barbershops and other appointment businesses that take bookings through this plugin, and for the agencies that look after those sites. You will get a plain-English explanation of the flaw, a quick way to tell if you are affected, the exact update steps, and a short check to see whether anyone has already abused it.

What is the Salon Booking System vulnerability?

The flaw is tracked as CVE-2026-110031. A CVE is a public ID number for a known security problem, so everyone can talk about the same bug. The record was published on 2026-10-18 in the National Vulnerability Database entry for CVE-2026-110031. At the time of writing, NVD lists its status as Deferred, which means NVD has not completed its own analysis of this record. The details below come from the description in that record. The WPScan entry for this bug is at https://wpscan.com/vulnerability/8d24ad5b-2d50-467b-9c40-45e86e53dafb/

In short, the plugin adds a custom user role for salon staff. When someone with that role edits a customer in the plugin, the plugin does not stop them from changing the capabilities of other accounts. A capability is a single permission in WordPress, such as editing posts or installing plugins. Per the record, that lets a staff user push any account up to administrator.

An administrator can do almost anything on a WordPress site. They can install plugins, edit code, create users and read data. That is why the record describes it as a way to take over the site.

The weakness type is CWE-269, which means improper privilege management. Put simply, the plugin let a user hand out permissions that the user should never be allowed to hand out. You can read the general definition at MITRE's CWE-269 page.

How serious is it?

The CVE record lists a severity of High (CVSS 7.2) (vector CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H). CVSS is a standard 0 to 10 scale for rating how bad a flaw is.

Two parts of that vector matter to you:

  • AV:N means it can be attempted over the network, so the attacker does not need to be in your building.
  • PR:H means the attacker needs high privileges first. The score treats a salon staff login as a privileged account.

That second point is the honest context. This is not a bug where a stranger with no login can walk in. Someone needs a staff account first. But many small businesses give staff accounts to several people, share logins, or reuse passwords. A staff password that leaks, gets guessed or is held by a person who has left on bad terms can be enough to matter here.

The record does not say that attacks are happening in the wild, and we are not claiming that. It simply says the bug exists in versions before 10.31.11. Treat it as a fix-this-week item, not a panic.

Who is affected?

The NVD record does not list a separate table of affected versions. Going only by the description, the affected group is every Salon Booking System version before 10.31.11.

Your situationAffected?What to do
Plugin version is below 10.31.11YesUpdate now, then run the checks below
Plugin version is 10.31.11 or newerThe described flaw is fixedRun the quick admin check anyway
Plugin is installed but deactivatedUpdate or delete itDo not leave old plugin code on the server
You have no accounts with the salon staff roleLower practical risk, since the attacker needs a staff-role account firstStill update. The flaw is in the plugin code, and a staff account could be added later
You do not use this pluginNot affected by this CVENothing to do

How to check your version

  1. Log in to your WordPress dashboard.
  2. Go to Plugins > Installed Plugins.
  3. Find Salon Booking System and read the version number under its name.

If you have command-line access, WP-CLI (the official WordPress command-line tool) shows it too. The plugin folder is normally called salon-booking-system. If the command below finds nothing, run wp plugin list and look for the right name.

wp plugin list --name=salon-booking-system --fields=name,status,version,update

How to fix it: update to 10.31.11 or later

The fix is a normal plugin update. Do it in this order.

  1. Take a backup first. Use your host's backup tool or a backup plugin. It takes a few minutes and gives you a safe way back if an update breaks something.
  2. Update the plugin. In the dashboard, go to Plugins > Installed Plugins and click Update now under Salon Booking System. Or run:
   wp plugin update salon-booking-system
  1. Confirm the version is 10.31.11 or higher.
  2. Test a booking. Make a test appointment on the front end and check that the confirmation and calendar work.
  3. Check the vendor's changelog on the plugin's page in the WordPress plugin directory. Because NVD's analysis is not complete, the changelog is the best place to see anything else changed in the release.

If the update button does not appear, go to Dashboard > Updates and click Check Again. If you manage the site through an agency or a host, send them the CVE number and ask them to confirm the version.

Updating closes the hole going forward. It does not undo anything that happened before you updated. That is why the next step matters.

Check whether someone already made themselves an admin

This check takes five minutes. It is worth doing even if you think nothing is wrong.

  1. Go to Users > All Users and click the Administrator filter at the top.
  2. Read every name and email. You should recognise each one.
  3. Look for new accounts, odd email addresses, or a staff or customer account that is now an administrator.

With WP-CLI, this lists all administrators with their sign-up dates:

wp user list --role=administrator --fields=ID,user_login,user_email,user_registered

To see every account and its role in one view, which helps you spot a staff or customer account that was promoted:

wp user list --fields=ID,user_login,user_email,roles

A role check alone is not enough. This flaw lets a staff user assign individual capabilities, so an account could hold extra permissions without showing the Administrator role. Also check non-admin accounts for unexpected capabilities. Replace USERNAME with the account's login name:

wp user list-caps USERNAME

Look for powerful capabilities such as install_plugins or manage_options on a staff or customer account that should not have them.

If you find an admin you do not recognise, or an account with capabilities it should not have:

  • Do not just delete it and move on. Note its name, email and sign-up date first, so you have a record.
  • Change the password of every real administrator and every staff account. Use long, unique passwords.
  • Log out all sessions for affected users. In the user's profile, use Log Out of All Sessions, or run wp user session destroy USERNAME --all.
  • Look at Plugins and Appearance for anything you did not install.
  • Follow our website hacked guide for the full clean-up steps.

A stray administrator is only one sign. Attackers who get admin access often add a backdoor, which is a hidden way back in, so a deeper check is smart if anything looks off.

Cut the risk from staff accounts

This bug is a good reminder that staff accounts are a real door into your site. A few habits shrink that risk, and they help against many other flaws too:

  • Give each person their own login. Never share one staff account between people.
  • Remove accounts when someone leaves. Do it the same day.
  • Use strong, unique passwords and a password manager.
  • Turn on two-factor authentication for administrators and staff if your site setup supports it.
  • Keep plugins updated and delete the ones you do not use. Out-of-date plugins and weak or stolen passwords are common causes of WordPress compromises.
  • Review your administrator list every month. It takes one minute.

This class of problem has a name: broken access control, where the software lets a user do something their role should not allow. It sits at the top of the OWASP Top 10, a respected list of common web risks. For how WordPress roles and capabilities are meant to work, see the official WordPress roles and capabilities documentation.

Why a scanner may not catch a bug like this

Automated tools are good at spotting old plugin versions. A free outside check can tell you which software your site shows to the world. Our free website security check does that kind of passive look. But a flaw like this one depends on how roles and permissions behave once someone is logged in. Finding the next one means a person testing with different user roles and trying to cross the lines between them. We explain the difference in manual vs automated penetration testing.

Key takeaways

  • Update Salon Booking System to 10.31.11 or later. Versions before that are affected, per the CVE-2026-110031 description.
  • The attacker needs a salon staff login first, but a leaked or shared staff password is enough to make this matter.
  • Updating does not undo past damage. Review Users > Administrator and change passwords if anything looks wrong.
  • Back up first, then test a booking after the update.
  • Keep staff accounts personal, remove them when people leave, and review admins monthly.

Want a human to look at your site?

This fix is simple, but it only covers one plugin. A real person testing your site by hand can check how your roles, logins and other plugins behave together. A Bug Circuit audit is a manual security test of one website that ends in a full written report with every issue, its severity, evidence and fix steps. It is $49 one-time on the Essential plan, and you can see all options on the pricing page. It is a focused small-site audit, not a multi-week enterprise test or a compliance certificate. We report the problems and explain the fixes. Fixing is a separate service, quoted per issue, and you pay only if you agree.

Want certainty, not guesswork?

A real human security engineer audits your whole site by hand and sends a full report: every issue, its severity, and the exact fix. From $49, with a 14-day money-back guarantee.

See pricing

Frequently asked questions

What is the Salon Booking System vulnerability?
CVE-2026-110031 is a flaw in the Salon Booking System WordPress plugin before version 10.31.11. A user with the plugin's salon staff role can assign arbitrary capabilities to other accounts while editing a customer. That lets them promote any account to administrator and take over the site.
Is there a Salon Booking System update 10.31.11 and should I install it?
Yes. According to the CVE record, the flaw affects versions before 10.31.11, so updating to 10.31.11 or later is the fix. Back up your site first, update from Plugins > Installed Plugins, then test a booking. Check the plugin's changelog for anything else in the release.
Can a WordPress booking plugin privilege escalation bug lead to site takeover?
Yes, it can. Privilege escalation means a user gains more permissions than they should have. If a low-level account can become an administrator, as this bug allows, that person can install plugins, edit code and read data. That is why updating promptly and reviewing your admin list matters.
Can a stranger exploit this bug without logging in?
Not according to the CVE record. The score assumes the attacker already holds high privileges, in this case a salon staff account. Still, a leaked, reused or shared staff password can supply that account, so treat the update as important.
How do I know if my site was already taken over through this flaw?
Check Users > All Users and filter by Administrator. Look for names or emails you do not recognise, or a staff or customer account that is now an admin. Also check non-admin accounts for unexpected capabilities with wp user list-caps USERNAME. If you find a problem, change all passwords, log out all sessions, review your plugins and follow a clean-up guide.

Keep reading

See what attackers see, for free

Run the free passive check on your website. No login, no impact on your site, results in seconds.

Ready for the full manual audit? See pricing

Published by Bug Circuit. Written with AI assistance and reviewed for accuracy before publishing.