CVE-2022-41790 is a medium severity (CVSS 4.3) missing authorization flaw in the WP Time Slots Booking Form plugin for WordPress, versions up to and including 1.1.76. Update to 1.1.77 or later. Check your installed version and apply the update through your normal change process.
What's affected
The record lists WP Time Slots Booking Form from CodePeople, from the first release through 1.1.76. Patchstack gives the patched version as 1.1.77. Patchstack gives the required privilege as Subscriber.
The record scores it 4.3 (Medium) with vector CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N. Patchstack labels its own priority Low. The weakness class is CWE-862 (Missing Authorization).
How to check if you're exposed
Start with an inventory. If you manage the site with WP-CLI, this lists every plugin with its version and whether an update is waiting:
wp plugin list --fields=name,status,version,update
Look for the folder wp-time-slots-booking-form. That folder name comes from the Patchstack entry for this issue, so confirm it matches what sits under wp-content on your site. Without WP-CLI, open the Plugins screen in the dashboard and read the version shown under the name. Version 1.1.76 or lower is affected. Version 1.1.77 or later is patched.
Check staging copies, old multisite subsites and inactive plugins too. A deactivated plugin is still on disk, and some of these bugs are reachable through files that load even when the plugin is switched off, so deactivation alone is not a fix. Delete what you do not use.
What to do now
- Update WP Time Slots Booking Form to 1.1.77 or a newer release.
- Review the site's user list and remove accounts you do not recognise.
- Turn on automatic updates for the plugin so the next fix lands without a ticket.
Why it matters
This is a small flaw with a small score: a logged in Subscriber can perform an action the plugin should have restricted, with low integrity impact and nothing on confidentiality or availability. Patchstack ranks its own priority Low.
The record does not say which action. I did not find that detail in the sources I read, so I leave it out. Booking plugins hold customer names and appointment data, so even small changes to bookings can disrupt a small business, and the fix is a single update.
Treat it as routine hygiene. If your update process is already automated, you may have it fixed by now. The record's KEV flag is false, and nothing I fetched reports exploitation in the wild.
Quick check
What does the vector mean in plain words?
Reachable over the network, easy to do, but it needs a low privilege account, and the only effect is a low integrity impact.
What is the fixed version?
Patchstack lists 1.1.77.
Sources
Safeguard can help you see this across many sites or repositories at once. Paste a manifest into the free in-browser dependency scan at gold.safeguard.sh/scan or look the issue up in the Gold directory to see how the record is tracked.
Last reviewed: 19 October 2026.