CVE-2026-27428
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 Eagle-Themes Eagle Booking eagle-booking allows SQL Injection.This issue affects Eagle Booking: from n/a through <= 1.3.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 · moderate confidenceSQL injection vulnerability in Eagle Booking plugin/theme up to version 1.3.4.3 allows attackers to inject malicious SQL commands through unsanitized user input in database queries, potentially enabling data exfiltration or unauthorized database manipulation.
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
- Low
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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.
-
Locate Eagle Booking installationSearch your web server for Eagle Booking theme or plugin files. Common paths include /wp-content/themes/eagle-booking/ for themes or /wp-content/plugins/eagle-booking/ for plugins.Affected if Eagle Booking theme or plugin files exist on the server
-
Determine installed versionOpen the main Eagle Booking PHP file (often named index.php, functions.php, or the theme/plugin root file) and locate the 'Version:' declaration in the file header comment.Affected if The declared version is 1.3.4.3 or any version lower than 1.3.4.3
-
Verify vulnerable query code existsSearch PHP files within the Eagle Booking directory for database query patterns. Look for instances of $wpdb->query, $wpdb->get_results, or similar direct query calls that incorporate user-supplied input from $_GET, $_POST, or $_REQUEST without using $wpdb->prepare() or other sanitization functions.Affected if Direct database queries contain unsanitized user input parameters
-
Confirm input parameters are exposedIdentify PHP files that process booking-related user input (such as search forms, booking submission handlers, or filter parameters) and verify whether these inputs are passed directly into SQL statements without validation or parameterization.Affected if User input from HTTP request parameters flows directly into SQL queries without sanitization
The environment is affected if Eagle Booking version 1.3.4.3 or lower is installed and contains database query code that handles user input without proper sanitization or prepared statements.
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 dataUpgrade to a patched version of Eagle Booking that implements proper input validation and parameterized queries, or audit and rewrite vulnerable database query code to use prepared statements throughout the application.
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27428 — 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-27428 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