dbcve.org
SQL InjectionWeakness · CWE-89

CVE-2026-15335

HIGH · 7.5 CVSS v3.1 Published 2026-07-11
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click 6 weeks old

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 · unedited
The Booking Package plugin for WordPress is vulnerable to generic SQL Injection via 'email' Form Parameter (form<N>) in all versions up to, and including, 1.7.20 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. The vulnerable REST API endpoint /wp-json/booking-package/v1/request is registered with permission_callback: __return_true and wp_magic_quotes does not apply to REST-sourced $_POST values, meaning single quotes in the payload reach the SQL sink intact without any authentication requirement. The impact of this is severely limited as the vulnerable parameter goes through is_email.

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 confidence

The Booking Package WordPress plugin versions up to 1.7.20 contain an unauthenticated SQL Injection vulnerability in the REST API endpoint /wp-json/booking-package/v1/request. The 'email' parameter is insufficiently escaped and reaches the SQL query without proper preparation. While the endpoint requires no authentication (permission_callback: __return_true), the impact is somewhat limited as the parameter passes through WordPress's is_email() validation.

MitigationUpdate the Booking Package plugin to version 1.7.21 or later which contains the patched version. If an update is not immediately possible, consider disabling the plugin or implementing a WAF rule to block SQL injection attempts against the vulnerable endpoint.

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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Booking Package plugin installation
    In WordPress admin, navigate to Plugins > Installed Plugins and locate 'Booking Package', or check the plugin files in wp-content/plugins/booking-package for a version file or header comment containing the version number
    Affected if The plugin is installed and the version displayed is 1.7.20 or lower
  2. Compare installed version to affected range
    Review the version number found - the vulnerable versions are up to and including 1.7.20. Versions 1.7.21 and later contain the patch
    Affected if The installed version is 1.7.20 or lower (for example, 1.7.19, 1.7.0, 1.6.5)
  3. Verify the vulnerable REST API endpoint exists
    Make a GET request to /wp-json/booking-package/v1/request or attempt to access this endpoint using curl or a web browser. The endpoint should respond if the plugin is active
    Affected if The endpoint responds with any JSON content, indicating the vulnerable API is accessible
  4. Confirm the email parameter accepts input
    Send a POST request to /wp-json/booking-package/v1/request with an 'email' parameter. Even though is_email() validation applies, the parameter should still accept and process input
    Affected if The endpoint accepts the email parameter and processes it (response may vary based on other required parameters)

A user is affected if the Booking Package plugin is installed with version 1.7.20 or lower and the /wp-json/booking-package/v1/request REST API endpoint is accessible and accepting the email parameter.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the Booking Package plugin to version 1.7.21 or later which contains the patched version. If an update is not immediately possible, consider disabling the plugin or implementing a WAF rule to block SQL injection attempts against the vulnerable endpoint.

Recommended fix Moderate confidence

Booking Package plugin version 1.7.21

  1. Upgrade the Booking Package plugin to version 1.7.21 or later, as the vulnerability is stated to exist in all versions up to and including 1.7.20

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-15335 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-15335 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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