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

Back
New CVE Detected

CVE-2026-57714 – Unauthenticated Blind SQL Injection – LatePoint WordPress Plugin ≤ 5.6.3

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

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-57714 is a critical Blind SQL Injection vulnerability in the LatePoint appointment booking plugin for WordPress, affecting all versions through 5.6.3. Carrying a CVSS v3.1 base score of 9.3 (Critical), the flaw requires no authentication and no user interaction, allowing any remote attacker to systematically extract sensitive data from the underlying WordPress database — with scope impact extending beyond the plugin’s own data. Sites running LatePoint on 100,000+ active installations worldwide are at risk and should upgrade immediately.

Technical details

  • Root cause: Improper neutralization of special elements used in SQL commands (CWE-89). Attacker-controlled input passed through the plugin’s publicly accessible booking endpoints is not adequately sanitized or parameterized before being incorporated into database queries.
  • Trigger conditions: Fully unauthenticated and requires no user interaction. Any remote, unauthenticated party with network access to the target site can trigger the vulnerability via standard HTTP/HTTPS requests to the booking interface.
  • Attack vector: Network (AV:N), low attack complexity (AC:L). LatePoint’s booking forms and scheduling endpoints are publicly exposed by design, giving attackers direct access to the vulnerable input vectors without needing credentials or any form of prior access.
  • Impact: Blind SQL Injection enables systematic, time- or boolean-based enumeration of the WordPress database. An attacker can extract customer PII, appointment records, stored credentials (including WordPress user password hashes), and payment metadata. The Changed scope (S:C) in the CVSS vector confirms the impact can extend beyond the plugin’s own database rows. Confidentiality impact is rated High (C:H), with an additional Low availability impact (A:L).

Affected software

  • LatePoint WordPress Plugin: all versions from n/a through 5.6.3 (inclusive)

Severity

  • CVSS v3.1 Base Score: 9.3 — Critical
  • Vector String: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:L

Mitigation and recommended actions

  • Immediate action — patch now: Update LatePoint to version 5.6.4 or later. The security fix was confirmed in the 5.6.4 release (June 30, 2026), as documented in the plugin’s official WordPress.org changelog. The current release as of this writing is 5.6.8.
  • If immediate patching is not feasible: Restrict unauthenticated access to LatePoint booking endpoints at the web application firewall (WAF) or network perimeter level until the update can be applied. This is a temporary measure only — patching remains the sole permanent remediation.

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

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

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

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

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge