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

New CVE Detected

CVE-2026-42667 – Unauthenticated Sensitive Data Exposure – Bookly WordPress Plugin <= 27.4

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

Summary

CVE-2026-42667 is a high-severity unauthenticated sensitive data exposure vulnerability affecting the Bookly WordPress plugin in all versions up to and including 27.4. Classified under CWE-201 (Insertion of Sensitive Information Into Sent Data), the flaw allows any remote, unauthenticated attacker to retrieve sensitive information directly from affected installations. With a CVSS v3.1 base score of 7.5 (HIGH) and over 60,000 active installations worldwide, this vulnerability presents significant risk to businesses relying on Bookly for appointment and scheduling management.

Technical details

  • Root cause: The plugin inserts sensitive information into data sent in HTTP responses without enforcing authentication, classified as CWE-201 (Insertion of Sensitive Information Into Sent Data).
  • Trigger conditions: An unauthenticated HTTP request to the affected endpoint is sufficient to trigger the data disclosure — no credentials, session token, or user interaction of any kind is required.
  • Attack vector: Network-accessible; exploitable directly from the internet against any publicly reachable WordPress site running an affected version of the plugin.
  • Impact: High confidentiality impact (C:H). The Bookly plugin manages customer booking records, contact details, service information, and appointment data, making exposed information potentially inclusive of customer personally identifiable information (PII). No integrity or availability impact has been reported.

Affected software

  • Bookly – Online Scheduling and Appointment Booking System (WordPress plugin), all versions <= 27.4

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

Mitigation and recommended actions

  • Immediate action: Update the Bookly plugin to version 27.5 or later. The current available version is 27.7. Updates can be applied directly from the WordPress admin dashboard under Plugins → Installed Plugins → Update Available.
  • If immediate patching is not possible:
    • Restrict public network access to the WordPress installation using a web application firewall (WAF) rule to block unauthenticated requests to the affected endpoint.

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