CVE-2026-1719
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 Gravity Bookings Premium plugin for WordPress is vulnerable to SQL Injection in all versions up to, and including, 2.5.9 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.
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 confidenceThe Gravity Bookings Premium WordPress plugin (versions up to 2.5.9) contains a SQL Injection vulnerability allowing unauthenticated attackers to inject arbitrary SQL queries through insufficiently escaped user-supplied parameters combined with unsafely prepared SQL queries. This can lead to sensitive data extraction from the database.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
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.
-
Identify if Gravity Bookings Premium plugin is installedCheck the WordPress plugins directory for the plugin folder (typically wp-content/plugins/gravity-bookings-premium/) or run: `wp plugin list --status=active --format=csv` if WP-CLI is availableAffected if The plugin folder exists in the WordPress installation's plugins directory
-
Determine the installed plugin versionOpen the main plugin file (gravity-bookings-premium.php) and locate the Version header in the plugin comment block, or run: `grep -i "Version:" wp-content/plugins/gravity-bookings-premium/gravity-bookings-premium.php`Affected if The version number returned is 2.5.9 or lower
-
Confirm the plugin is activeCheck the WordPress database wp_options table for the active_plugins option, or run: `wp plugin is-active gravity-bookings-premium` if WP-CLI is availableAffected if The plugin appears in the list of active plugins in the WordPress site
-
Verify the vulnerable parameter is reachableReview plugin source code for handlers that process user-supplied parameters (GET/POST requests) and check if they are used in SQL queries without proper prepare() statements; common entry points include form submission handlers or booking lookup functionsAffected if User-supplied parameters from HTTP requests are directly concatenated into SQL queries without escaping or prepare() usage
A user is affected if the Gravity Bookings Premium plugin is installed, active, and running version 2.5.9 or lower where unsanitized user input reaches SQL query execution.
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.
From vendor dataUpdate the Gravity Bookings Premium plugin to version 2.6.0 or later which patches the SQL injection vulnerability. If immediate patching is not feasible, disable the plugin until the update can be applied.
- Consultation2.0 h
- Implementation2.0 h
- Testing2.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,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-1719 — 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-2026-1719 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