Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin <= 1.6.11.11 - Missing Authorization
Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin misses an authorization check. A logged-in user can do an action they should not be allowed to do.
Quick answer
Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin should be reviewed and updated if it matches the affected versions. The recommended fix is to apply the vendor-supported patched version or the mitigation steps below, then retest the public website with Fixnx.
Who is affected
Affected versions
- Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin up to and including 1.6.11.11
Fixed versions
- Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin 1.6.12.0 or later
How to fix it
Update Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin. The old version lets a logged-in user do something they should not be allowed to do.
- Back up the site and database.
- Update Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin to Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin 1.6.12.0 or later.
- Review user roles and lower access for users who do not need it.
- Check recent changes made by low-privilege accounts.
Scan now. Google sign-in is only needed to unlock fix guidance.
Verify the fix
- Confirm the installed version is Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin 1.6.12.0 or later.
- Test with a subscriber or customer account and confirm the action is blocked.
Related categories
Trusted references
FAQ
What is affected by CVE-2026-59523?
Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin versions listed as affected should be reviewed: Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin up to and including 1.6.11.11.
What should I fix first?
Start with internet-facing sites, admin panels, login flows, plugins, themes, modules, packages, and systems that process user-controlled input or sensitive data.
How do I confirm the fix worked?
Apply the patched version or mitigation, clear caches where relevant, retest the affected workflow, and run a new Fixnx scan to verify public website exposure signals.
How are Fixnx security risk categories chosen?
Fixnx keeps one canonical risk page and assigns only broad, relevant categories such as ecosystem, technology area, or vulnerability class.