Blog

"Prevention is cheaper than a breach"

Home / Threats / CVE-2026-9830

CVE-2026-9830 - Before 5 Plugin

CVE-2026-9830

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.

CVE-2026-9830

UNKNOWN CVSS 0.0 Published 2026-07-27 Updated 2026-07-27
AI Risk Low (6/100) Active Exploit: No strong signal Published Exploit: No public exploit references Priority: P5 Monitor
Severity Band UNKNOWN
CVSS Vector Unspecified
Affected Components 2
Reference Links 1
AI Risk Engine Low (6/100)
Exploitability Low
Active Exploitation No strong signal
Published Exploit Status No public exploit references

Threat Timeline

  1. 2026-07-27 CVE published and first recorded in the threat feed.
  2. 2026-07-27 Record updated with latest vulnerability metadata.
  3. 2026-07-27 AI technical context refreshed for mitigation and impact guidance.
  4. Now Monitoring for follow-up changes, linked references, and new related CVEs.

AI Context

Machine-generated threat intelligence

AI Updated 1 hour ago

AI enriched 1 hour ago (2026-07-27 19:13 UTC)

Technical Summary

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.

Potential Impact

Severity is UNKNOWN (CVSS 0.0). Depending on deployment context, affected components may be exposed to unauthorized actions or data integrity risk.

Exploitability Assessment

Exploitability is assessed as Low based on low-bar exploit prerequisites.

Primary risk drivers: low-bar exploit prerequisites

Mitigation Recommendations

Validate affected product versions, prioritize patching, and monitor references for vendor remediation guidance. If immediate patching is not possible, apply compensating controls and limit exposure of vulnerable surfaces.

Detection & Monitoring

Track authentication anomalies, unexpected file writes, and suspicious plugin API activity around affected components.

Business Impact Lens

AI risk score 6/100 (Low, Low) with priority P5 Monitor. Prioritize remediation where affected components process customer data, admin sessions, or Internet-exposed workflows.

Scroll to top