BookitWordPress extension · Stylemixthemes
CVE-2023-50852
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedImproper Neutralization of Special Elements used in an SQL Command ('SQL Injection') vulnerability in StylemixThemes Booking Calendar | Appointment Booking | BookIt.This issue affects Booking Calendar | Appointment Booking | BookIt: from n/a through 2.4.3.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceSQL injection vulnerability in StylemixThemes BookIt Booking Calendar plugin allows attackers to inject malicious SQL commands via unsanitized input in the booking/appointment functionality. The improper neutralization of special elements in SQL queries enables unauthorized database access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
BookitWordPress extension
< 2.4.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify BookIt plugin is installedNavigate to WordPress admin panel > Plugins > Installed Plugins, or inspect the file system for /wp-content/plugins/bookit/ directoryAffected if The BookIt plugin directory exists and the plugin is active on the WordPress site
-
Check installed versionIn WordPress admin, go to Plugins > Installed Plugins and locate BookIt to view the version number, or check the main plugin file header in /wp-content/plugins/bookit/bookit.php for the 'Version' fieldAffected if The version number is lower than 2.4.4 (e.g., 2.4.3, 2.4.0, 1.x.x)
-
Verify booking functionality is accessibleCheck if the booking/appointment submission form is published and accessible on the frontend (typically via shortcode [bookit-form] or widget), or check for exposed booking endpoints in the REST APIAffected if The booking form is publicly accessible and accepts user input for appointment reservations
If the BookIt plugin is installed with version lower than 2.4.4 and the booking form is active and accessible, the environment is affected by this SQL injection vulnerability.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped2.4.4
Replace dynamic SQL queries with parameterized queries/prepared statements, implement proper input validation and sanitization, and update to the latest patched version of the plugin when available.
2.4.4
- Update the Bookit (Booking Calendar | Appointment Booking | BookIt) plugin to version 2.4.4 or later
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Bookit
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50852 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2023-50852 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data