WordPress Booking Plugin SQL Injection via Parameter Escaping

The Appointment Booking Calendar — Simply Schedule Appointments Booking Plugin plugin for WordPress is vulnerable to time-based blind SQL Injection via the 'append_where_sql' parameter in all versions up to, and including, 1.6.11.8 due to insufficient escaping on the user supplied parameter and lack of sufficient preparation on the existing SQL query. This makes it possible for unauthenticated attackers to append additional SQL queries into already existing queries that can be used to extract sensitive information from the database. The /appointments/bulk REST endpoint is reachable by unauthenticated attackers because its permission check accepts a public nonce that is embedded in the booking widget's frontend JavaScript (ssa.api.public_nonce) and visible to all site visitors; exploitation requires issuing the request as a PUT with an application/x-www-form-urlencoded body so that PHP's superglobals are not populated and the blocklist check silently passes.

Casky was already ahead

This CVE exploits attack patterns that Casky's 301matched skills already investigate — long before this vulnerability was disclosed. Claude's reasoning model maps these techniques to MITRE ATT&CK, so practitioners who ran these skills have already seen the threat behaviour in their findings.

Analysis

The Appointment Booking Calendar — Simply Schedule Appointments plugin for WordPress contains a time-based blind SQL injection vulnerability affecting all versions up to 1.6.11.8. An unauthenticated attacker can exploit insufficient escaping of the 'append_where_sql' parameter to inject malicious SQL commands into existing queries. This vulnerability is particularly dangerous because it requires no authentication, making it accessible to any threat actor, and enables data extraction including sensitive information like user credentials, appointment details, and potentially database admin accounts. Organizations running this plugin on WordPress sites face immediate risk of data breach and unauthorized database manipulation.

Casky's 301 mapped security skills leverage Claude AI with extended reasoning to detect the exploitation patterns associated with MITRE techniques TA0001 (Reconnaissance) and TA0043 (Reconnaissance) through SQL injection attack signatures. Practitioners using Casky will observe findings that correlate suspicious HTTP requests containing SQL metacharacters and time-delay patterns in the 'append_where_sql' parameter, combined with abnormal database query execution timings. The platform identifies reconnaissance activities typical of blind SQL injection testing—sequential parameter manipulation attempting to infer database structure—and flags the progression from information gathering to potential data exfiltration, enabling security teams to detect and respond to exploitation attempts before sensitive data is compromised.

Live Threat IntelligenceComing soon

Casky Risk Score

—

EPSS Probability

—

Shodan Exposure

—

GreyNoise Signal

—

Composite risk scoring from EPSS, CISA KEV, Shodan, and GreyNoise — 21 security APIs correlated into a single Casky Risk Score. Coming in Casky Pro. Join early access →

301 Casky skills cover this attack pattern

These skills use Claude AI's reasoning model to surface findings in the same attack categories as CVE-2026-7797.

analyzing-apt-group-with-mitre-navigator

threat intelligence · low

Run

analyzing-campaign-attribution-evidence

threat intelligence · low

Run

analyzing-certificate-transparency-for-phishing

threat intelligence · low

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-7797

Casky has 301 skills that investigate the attack patterns behind CVE-2026-7797. Run one and get CVSS-scored findings in 3 minutes.

Run the skill that detects this →

X Instagram LinkedIn