WordPress TrueBooker Plugin SQL Injection via User Parameter

The TrueBooker – Appointment Booking and Scheduler System plugin for WordPress is vulnerable to generic SQL Injection via the 'alldata[truebooker_user]' parameter in all versions up to, and including, 1.2.2 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 check_ajax_referer() nonce guard does not constitute an authentication or authorization barrier because the nonce is exposed to unauthenticated visitors on TrueBooker front-end booking pages; exploitation additionally requires that the required booking fields (category, service, person, date, and time slot) be present in the alldata POST parameter so that execution reaches the vulnerable SQL query branch.

Casky was already ahead

This CVE exploits attack patterns that Casky's 322matched 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 TrueBooker appointment booking plugin for WordPress contains a critical SQL injection vulnerability in the 'alldata[truebooker_user]' parameter affecting all versions through 1.2.2. This vulnerability exists because user-supplied input is insufficiently escaped and SQL queries lack proper parameterization, allowing unauthenticated attackers to inject arbitrary SQL commands. The impact is severe: adversaries can extract sensitive data from the WordPress database including user credentials, appointment details, and potentially payment information. This affects any WordPress installation running the vulnerable plugin, with no authentication required to exploit the flaw.

Casky's 322 matched skills leverage Claude's extended reasoning to detect the attack patterns mapped to MITRE ATT&CK techniques TA0001 (Initial Access) and TA0043 (Reconnaissance). Practitioners using Casky would identify this vulnerability through detection of CWE-89 SQL Injection patterns—specifically unusual SQL syntax in request parameters, union-based query attempts, and time-based blind SQL injection indicators in logs. The platform would correlate these techniques with reconnaissance activities (TA0043) where attackers probe for database structure and information disclosure (TA0001) as an initial access vector. Practitioners would see flagged requests containing SQL keywords, nested queries, or comment sequences in the 'alldata[truebooker_user]' parameter, enabling them to prioritize patching to version 1.2.3 or later and implement Web Application Firewall rules to block injection attempts.

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 →

322 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-13161.

Abuse of Public-Facing API: Mobile API Abuse

mobile security · low

Run

abusing-dpapi-for-credential-access

red teaming · high

Run

abusing-shadow-credentials-for-privesc

red teaming · high

Run

MITRE ATT&CK Techniques

TA0001 TA0043

Investigate the attack patterns behind CVE-2026-13161

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

Run the skill that detects this →

X Instagram LinkedIn