CVE-2026-13161: TrueBooker (WordPress plugin) · SQL Injection
Affects TrueBooker (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 7.5 High.
Data as of 27 Oct 2026, 05:11 UTC
- EPSS
- 0.7% chance of exploitation in 30 days – higher than 55% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:NExploitation evidence
Disclosed: evidence found.
CVE published 28 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| themetechmountTrueBooker – Appointment Booking and Scheduler System | Affected
| Fixed in– |
AI-suggested
Until an official fix is available, restrict access to the plugin or disable it if possible. Monitor for updates from the vendor themetechmount and apply patches promptly once released. Avoid exposing the vulnerable plugin on publicly accessible sites without additional protective controls.
Description
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.
References
- wordfence.com/threat-intel/vulnerabilities/id/9b0e973b-f0bf-44d1-b964-e259f68291aa?source=cve (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.0/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.2/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.2/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.2/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.0/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/browser/truebooker-appointment-booking/tags/1.2.0/main/function_ajax.php (opens in a new tab)
- plugins.trac.wordpress.org/changeset?sfp_email=&sfph_mail=&reponame=&new=3591506%40truebooker-appointment-booking%2Ftrunk%2Fmain%2Ffunction_ajax.php&old=3581699%40truebooker-appointment-booking%2Ftrunk%2Fmain%2Ffunction_ajax.php&sfp_email=&sfph_mail= (opens in a new tab)