Ctrl Booking For Elementor Security & Risk Analysis

wordpress.org/plugins/ctrl-booking-system

A flexible booking system for businesses, seamlessly integrated with Elementor for easy customization and user-friendly management.

0 active installs v1.0.0 PHP 7.4+ WP 6.2+ Updated Unknown
appointmentsbookingbooking-systemcalendarelementor
100
A · Safe
CVEs total0
Unpatched0
Last CVENever
Safety Verdict

Is Ctrl Booking For Elementor Safe to Use in 2026?

Generally Safe

Score 100/100

Ctrl Booking For Elementor has no known CVEs and is actively maintained. It's a solid choice for most WordPress installations.

No known CVEs
Risk Assessment

The "ctrl-booking-system" plugin version 1.0.0 exhibits a generally good security posture with strong adherence to best practices in most areas. The plugin demonstrates excellent output escaping (97%) and a high percentage of SQL queries using prepared statements (91%). File operations and external HTTP requests are absent, which are common sources of vulnerabilities. Furthermore, the absence of any recorded CVEs, particularly critical or high severity ones, is a significant positive indicator of its security over time.

However, there are specific areas of concern that warrant attention. The plugin exposes 8 AJAX handlers, with a notable 3 of them lacking proper authentication checks. This significantly increases the attack surface. While the taint analysis only identified one flow with unsanitized paths, the severity was not explicitly stated as critical or high, but the presence of any unsanitized path is a potential risk. The limited capability checks (1) in conjunction with the unprotected AJAX handlers also present a weakness. Despite the plugin's otherwise positive history, these unprotected entry points could be leveraged for various attacks if not adequately secured.

In conclusion, "ctrl-booking-system" v1.0.0 is a plugin with a promising security foundation, evidenced by its robust output escaping, prepared SQL statements, and lack of historical vulnerabilities. However, the unauthenticated AJAX handlers represent a critical flaw that must be addressed to mitigate significant risks. Addressing these specific entry points would elevate the plugin's overall security to a much stronger level.

Key Concerns

  • AJAX handlers without auth checks
  • Flow with unsanitized paths
  • Limited capability checks
Vulnerabilities
None known

Ctrl Booking For Elementor Security Vulnerabilities

No known vulnerabilities — this is a good sign.
Code Analysis
Analyzed Mar 17, 2026

Ctrl Booking For Elementor Code Analysis

Dangerous Functions
0
Raw SQL Queries
2
21 prepared
Unescaped Output
6
232 escaped
Nonce Checks
6
Capability Checks
1
File Operations
0
External Requests
0
Bundled Libraries
0

SQL Query Safety

91% prepared23 total queries

Output Escaping

97% escaped238 total outputs
Data Flows
1 unsanitized

Data Flow Analysis

1 flows1 with unsanitized paths
<admin> (includes\admin.php:0)
Source (user input) Sink (dangerous op) Sanitizer Transform Unsanitized Sanitized
Attack Surface
3 unprotected

Ctrl Booking For Elementor Attack Surface

Entry Points10
Unprotected3

AJAX Handlers 8

authwp_ajax_get_servicesincludes\ajax-handlers.php:44
noprivwp_ajax_get_servicesincludes\ajax-handlers.php:45
authwp_ajax_ctrlbs_admin_actionincludes\ajax-handlers.php:132
authwp_ajax_dismiss_donation_noticeincludes\ajax-handlers.php:137
authwp_ajax_get_time_slotsincludes\ajax-handlers.php:182
noprivwp_ajax_get_time_slotsincludes\ajax-handlers.php:183
authwp_ajax_ctrlbs_booking_submitincludes\ajax-handlers.php:237
noprivwp_ajax_ctrlbs_booking_submitincludes\ajax-handlers.php:238

Shortcodes 2

[ctrlbs_booking_form] booking-system.php:151
[ctrlbs_booking_form] includes\shortcodes.php:51
WordPress Hooks 11
actionadmin_enqueue_scriptsbooking-system.php:78
actionwp_enqueue_scriptsbooking-system.php:131
actionelementor/frontend/after_enqueue_stylesbooking-system.php:145
actioninitbooking-system.php:153
actionelementor/widgets/registerbooking-system.php:165
actionadmin_menuincludes\admin.php:59
actionadmin_post_save_ctrlbs_settingsincludes\admin.php:64
actionphpmailer_initincludes\email.php:10
actionadmin_noticesincludes\security.php:53
actionadmin_initincludes\settings.php:41
actionadmin_noticesincludes\template-functions.php:74
Maintenance & Trust

Ctrl Booking For Elementor Maintenance & Trust

Maintenance Signals

WordPress version tested6.7.5
Last updatedUnknown
PHP min version7.4
Downloads288

Community Trust

Rating0/100
Number of ratings0
Active installs0
Developer Profile

Ctrl Booking For Elementor Developer Profile

ctrldigitaltech

1 plugin · 0 total installs

94
trust score
Avg Security Score
100/100
Avg Patch Time
30 days
View full developer profile
Detection Fingerprints

How We Detect Ctrl Booking For Elementor

Patterns used to identify this plugin on WordPress sites during automated security audits and web crawling.

Asset Fingerprints

Asset Paths
/wp-content/plugins/ctrl-booking-system/assets/css/admin.css/wp-content/plugins/ctrl-booking-system/assets/css/stats.css/wp-content/plugins/ctrl-booking-system/assets/js/admin-script.js/wp-content/plugins/ctrl-booking-system/assets/css/style.css/wp-content/plugins/ctrl-booking-system/assets/js/script.js/wp-content/plugins/ctrl-booking-system/assets/css/elementor-widget.css
Script Paths
/wp-content/plugins/ctrl-booking-system/assets/js/admin-script.js/wp-content/plugins/ctrl-booking-system/assets/js/script.js
Version Parameters
?ver=1.0.0

HTML / DOM Fingerprints

CSS Classes
ctrlbs-form-widgetctrlbs-form
Data Attributes
data-nonce
JS Globals
ctrlbsNoncectrlbsAjax
Shortcode Output
<div class="ctrlbs-form-widget"> <form id="ctrlbs-booking-form" class="ctrlbs-form">
FAQ

Frequently Asked Questions about Ctrl Booking For Elementor