CVE-2026-54820
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 · uneditedUnauthenticated SQL Injection in JetBooking <= 4.0.4.1 versions.
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 · moderate confidenceUnauthenticated SQL Injection vulnerability in JetBooking WordPress plugin versions 4.0.4.1 and earlier allows remote attackers to inject malicious SQL queries via unsanitized input parameters, potentially enabling data exfiltration or database compromise.
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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L
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 JetBooking plugin is installedCheck the WordPress plugins directory (wp-content/plugins/) for the jetbooking folder, or query the wp_plugins database table for 'jetbooking' entryAffected if JetBooking plugin files exist in the WordPress installation
-
Determine installed JetBooking versionOpen the main plugin file (typically jetbooking.php) and look for the 'Version' header in the plugin comment block, or check the readme.txt fileAffected if Version is 4.0.4.1 or lower, or version cannot be determined (indicating an old or modified installation)
-
Confirm plugin is activeQuery the wp_options table for option_name='active_plugins' and check if jetbooking is in the serialized array, or check via WordPress admin dashboardAffected if Plugin is active - the vulnerability is unauthenticated, so it can be exploited even without admin access
-
Inspect HTTP request parameters for SQL injection vectorsReview web server access logs for requests to JetBooking endpoints (typically /?jet_action=* or /wp-json/jetbooking/*) and examine URL parameters for SQL syntax patterns (quotes, UNION, SELECT, comments like -- or /*)Affected if Suspicious SQL syntax found in request parameters to JetBooking URLs
-
Check for signs of database compromiseReview database tables for unexpected new admin accounts, unknown tables, or unusual data exports; also check WordPress user table (wp_users) for unauthorized additionsAffected if Unknown admin accounts, unusual tables, or evidence of data access beyond normal usage patterns
A user is affected if JetBooking plugin versions 4.0.4.1 or earlier are installed and active, exposing unauthenticated SQL injection vectors that could be detected via log analysis or database integrity checks.
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 JetBooking to the latest version; if unavailable, disable the plugin until a patch is released. The fix requires implementing parameterized queries or prepared statements for all database interactions.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-54820 — 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-54820 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