Booking Calendar Contact FormWordPress extension · Codepeople
CVE-2016-10909
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 · uneditedThe booking-calendar-contact-form plugin before 1.0.24 for WordPress has SQL injection.
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 the booking-calendar-contact-form WordPress plugin affecting versions prior to 1.0.24, allowing attackers to inject malicious SQL queries through unsanitized user input.
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
Booking Calendar Contact FormWordPress extension
< 1.0.24CVSS 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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/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.
-
Check if Booking Calendar Contact Form plugin is installedAccess your WordPress admin panel and navigate to Plugins > Installed Plugins. Look for 'Booking Calendar Contact Form' or 'booking-calendar-contact-form' in the list.Affected if The plugin appears in the installed plugins list
-
Verify the installed plugin versionIn the Plugins list, click on the plugin name or view its details to read the Version number displayed in the plugin header.Affected if The displayed version number is lower than 1.0.24 (e.g., 1.0.23, 1.0.10, etc.)
-
Confirm the plugin is activeIn the WordPress Plugins admin page, check that the plugin has a 'Deactivate' link rather than an 'Activate' link, indicating it is currently enabled.Affected if The plugin is activated and running on the site
-
Check for unsanitized booking form submissionsInspect the plugin source code in wp-content/plugins/booking-calendar-contact-form/ for SQL query parameters that accept user input without proper escaping (e.g., direct use of $_POST or $_GET in SQL statements).Affected if The plugin code contains SQL queries using unsanitized user input from booking form fields
Your site is affected if the Booking Calendar Contact Form plugin is installed, activated, and running a version lower than 1.0.24.
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 · scoped1.0.24
Update the booking-calendar-contact-form plugin to version 1.0.24 or later to apply the security patch.
Booking Calendar Contact Form version 1.0.24 or later
- Log in to the WordPress admin dashboard
- Navigate to Plugins > Installed Plugins
- Find 'Booking Calendar Contact Form' in the plugin list
- Check if the current version is below 1.0.24
- If vulnerable, click 'Update Now' or navigate to the plugin's page to download version 1.0.24 or later
- Verify the update completed successfully
- Test booking calendar functionality to confirm the plugin works correctly after update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Booking Calendar Contact Form
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-10909 — 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-2016-10909 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