Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB
CVE-2026-105198 Overview
CVE-2026-105198 is an Insecure Direct Object Reference (IDOR) vulnerability [CWE-639] affecting the Appointment Booking Plugin for WordPress in versions prior to 5.7.3. The plugin fails to verify that the caller owns the order referenced by an order-item identifier before rendering the order's confirmation summary. An unauthenticated visitor can supply a sequential order-item id and retrieve any customer's name, contact details, and order confirmation code. The flaw exposes personally identifiable information (PII) belonging to booking customers without requiring authentication or user interaction.
Critical Impact
Unauthenticated attackers can enumerate sequential order-item identifiers to harvest customer names, contact details, and confirmation codes from any WordPress site running the vulnerable plugin.
Affected Products
- Appointment Booking Plugin for WordPress versions before 5.7.3
- WordPress sites with the plugin installed and active
- Customer booking records stored by the plugin
Discovery Timeline
- 2026-10-08 - CVE-2026-105198 published to the National Vulnerability Database
- 2026-10-08 - Last updated in NVD database
Technical Details for CVE-2026-105198
Vulnerability Analysis
The vulnerability resides in the plugin's order confirmation summary endpoint. The endpoint accepts an order-item identifier passed by the client and returns the associated booking details without validating that the requester owns or is authorized to view that record. Because order-item identifiers are issued sequentially, an attacker can iterate through numeric values to enumerate the entire customer database. The exposed data includes customer names, contact details, and order confirmation codes, which can enable follow-on social engineering or fraudulent appointment manipulation. Attack complexity is low and no privileges or user interaction are required.
Root Cause
The root cause is missing authorization logic in the request handler that renders order confirmation summaries. The plugin treats possession of an order-item identifier as proof of ownership rather than cross-checking the identifier against the current session, a signed token, or a user capability. This pattern maps directly to CWE-639: Authorization Bypass Through User-Controlled Key.
Attack Vector
An unauthenticated remote attacker sends HTTP requests to the plugin's order confirmation endpoint, substituting different sequential integers for the order-item identifier parameter. The server returns the confirmation summary for whichever record matches, regardless of session context. Automation of this process allows bulk extraction of customer data at scale. Refer to the WPScan Vulnerability Report for additional technical context.
Detection Methods for CVE-2026-105198
Indicators of Compromise
- Repeated HTTP GET or POST requests to the plugin's order confirmation endpoint with incrementing order-item identifier values from the same source IP or user agent
- Access log entries showing unauthenticated requests retrieving confirmation summaries outside of normal customer booking workflows
- Spikes in outbound response size from the WordPress host correlated with sequential parameter enumeration
Detection Strategies
- Review WordPress and web server access logs for enumeration patterns against the Appointment Booking Plugin's confirmation URL
- Deploy a Web Application Firewall (WAF) rule that flags sequential numeric parameter patterns in requests to plugin endpoints
- Correlate request volume against unique session or cookie values to surface unauthenticated bulk access
Monitoring Recommendations
- Enable verbose logging on the WordPress site and forward logs to a central SIEM for anomaly analysis
- Alert on sustained request rates from a single IP targeting booking plugin endpoints
- Monitor for data egress spikes that may indicate scripted scraping of customer records
How to Mitigate CVE-2026-105198
Immediate Actions Required
- Upgrade the Appointment Booking Plugin to version 5.7.3 or later on all WordPress installations
- Audit access logs for signs of prior enumeration against the plugin's confirmation endpoint
- Notify affected customers if evidence of unauthorized data access is identified
Patch Information
The vendor addressed the issue in Appointment Booking Plugin version 5.7.3 by enforcing ownership checks before rendering the order confirmation summary. Site administrators should apply the update through the WordPress plugin manager. See the WPScan Vulnerability Report for advisory details.
Workarounds
- Temporarily deactivate the Appointment Booking Plugin until the patch is applied if upgrading is not immediately possible
- Place the booking confirmation endpoint behind a WAF rule that requires a valid session cookie or referrer header
- Restrict access to the booking confirmation URL via server-side authentication where feasible
# Example WAF rule concept to block unauthenticated sequential enumeration
# ModSecurity-style pseudo-rule - adapt to your WAF syntax
SecRule REQUEST_URI "@contains /appointment-booking/confirmation" \
"id:1050198,phase:1,deny,status:403,\
chain,msg:'Potential IDOR enumeration against Appointment Booking Plugin'"
SecRule &REQUEST_COOKIES:wordpress_logged_in "@eq 0"
Disclaimer: This content was generated using AI. While we strive for accuracy, please verify critical information with official sources.
Sources: National Vulnerability Database, CISA KEV, Exploit-DB

