Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-15335 – Unauthenticated SQL Injection – Booking Package WordPress Plugin (≤ 1.7.20)

Be the first to know when new zero-days emerge:

Summary

CVE-2026-15335 is a high-severity unauthenticated SQL injection vulnerability in the Booking Package plugin for WordPress (by MASAAKI TANAKA), affecting all versions up to and including 1.7.20. The flaw resides in the plugin’s publicly accessible REST API booking endpoint and allows unauthenticated remote attackers to append malicious SQL to existing queries and extract sensitive data from the database. The vulnerability carries a CVSS v3.1 score of 7.5 (HIGH).

Technical details

  • Root cause: Insufficient escaping of user-supplied input combined with improper SQL query preparation in the handling of the email form parameter (form<N>). WordPress’s wp_magic_quotes sanitisation does not apply to REST API $_POST values, meaning single quotes in the payload reach the SQL sink unescaped.
  • Trigger condition: The vulnerable REST API endpoint /wp-json/booking-package/v1/request is registered with permission_callback: __return_true, making it fully publicly accessible with no authentication requirement whatsoever.
  • Attack vector: Network — an unauthenticated remote attacker sends a crafted HTTP POST request to the REST API endpoint with a malicious email field. WordPress’s is_email() validation places format constraints on the payload (requiring a structurally valid email address), which increases exploitation complexity but does not prevent injection — RFC 5321 permits characters including single quotes in the email local-part, allowing payloads such as a'[SQL]@x.com.
  • Impact: Successful exploitation enables an attacker to read and exfiltrate arbitrary data from the WordPress database, including customer booking records, personally identifiable information, and WordPress user credentials (hashed passwords). Integrity and availability are not impacted (C:H/I:N/A:N).

Affected software

  • Booking Package WordPress plugin by MASAAKI TANAKA — all versions up to and including 1.7.20

Severity

  • CVSS v3.1 Base Score: 7.5 (HIGH)
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
  • CWE: CWE-89 – Improper Neutralization of Special Elements used in an SQL Command

Mitigation and recommended actions

  • Immediate action — patch now: Update the Booking Package plugin to version 1.7.21 or later. The WordPress.org plugin changelog for version 1.7.21 (released July 10, 2026) explicitly notes a security vulnerability fix. The updated plugin is available directly from the WordPress Plugin Repository.
  • If immediate patching is not possible: Restrict external network access to the REST API namespace /wp-json/booking-package/ via WAF rules or web server configuration until the plugin can be updated. Note that this may affect legitimate booking functionality.
  • General hardening: Audit all internet-exposed WordPress instances for outdated plugin versions. The plugin has over 10,000 active installations, making unpatched deployments a broad-surface target.

IONIX Status

The IONIX research team is tracking ongoing exploitation attempts and recommends immediate patching. Potentially affected assets are outlined in this post.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge