bookingpress-appointment-booking-pro: Improper Authentication
CVE-2026-9830 is a high-severity improper authentication vulnerability in bookingpress-appointment-booking-pro, with a CVSS 3.1 base score of 8.2 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists version 5.7.3 as the first without the flaw, so updating bookingpress-appointment-booking-pro to that release or later removes the exposure. There is no confirmed exploitation so far. EPSS estimates a 1.26% chance of exploitation within 30 days, higher than 70% of scored CVEs.
High severity with no evidence of exploitation so far.
What to do
- Update bookingpress-appointment-booking-pro to 5.7.3 or a later version.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Bookingpress-appointment-booking-pro | bookingpress-appointment-booking-pro | before 5.7.3 | 5.7.3 |
Version data comes from the organisation that assigned the CVE. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Attack vector
- NetworkCan be exploited remotely over a network, including the internet.
- Attack complexity
- LowNo special conditions are needed; the attack works reliably.
- Privileges required
- NoneNo account or login is needed.
- User interaction
- NoneNo action by a victim is required.
- Scope
- UnchangedImpact stays within the vulnerable component.
- Confidentiality
- HighAll data handled by the component can be read.
- Integrity
- LowLimited modification of data is possible.
- Availability
- NoneAvailability is not affected.
Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:N. Scored by CISA (ADP).
Official description
The bookingpress-appointment-booking-pro WordPress plugin before 5.7.3 does not correctly invoke its REST permission callback, leaving every route in one of its API namespaces reachable without authentication and allowing unauthenticated attackers to read customer booking data and modify other users' bookings.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Authentication
When an actor claims to have a given identity, the product does not prove or insufficiently proves that the claim is correct.
How developers prevent this class of flaw
- Use an authentication framework or library such as the OWASP ESAPI Authentication feature.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: poc, automatable: yes, technical impact: partial).
References
Other references
Recent Improper Authentication vulnerabilities
- 8.8 High severity
- 9.1 Critical severity
- 7.5 High severity
- 8.1 High severity
- 8.4 High severity
- 9.1 Critical severity
Spotted an error? Tell us.