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

New CVE Detected

CVE-2026-92966 – Unauthenticated Arbitrary Shortcode Execution (Code Injection) – LatePoint WordPres

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

Summary

CVE-2026-92966 is a critical code injection vulnerability (CWE-94, Improper Control of Generation of Code) affecting the LatePoint – Calendar & Scheduling Appointment Booking plugin for WordPress. The plugin fails to validate input submitted through its unauthenticated booking form, allowing an attacker to plant malicious shortcode payloads that are later executed on the site. The flaw carries a CVSS v3.1 base score of 9.1 (Critical) and requires no authentication or user interaction to exploit.

Technical details

  • Root cause: LatePoint does not sanitize or validate the first/last name fields submitted through its public booking form before storing and later re-rendering them.
  • Trigger conditions: An attacker submits a booking request containing a shortcode payload in the name fields. The payload is persisted and later rendered by the Customer Cabinet block via render_customer_dashboard(), which outputs the stored name into the content stream where WordPress core’s do_shortcode filter (running at priority 11) re-parses and executes it.
  • Attack vector: Network-based, unauthenticated — the booking form is publicly accessible on any site running the plugin.
  • Impact: Successful exploitation allows execution of arbitrary registered shortcodes in the WordPress context, leading to full compromise of confidentiality and integrity of site data (e.g., information disclosure, and depending on installed shortcodes/plugins, potential escalation to further compromise). Availability is not impacted.

Affected software

  • Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress: versions 0 through 5.7.0 (inclusive)

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N

Mitigation and recommended actions

  • Immediate: Upgrade the LatePoint plugin to version 5.7.1 or later, where the input used in the Customer Cabinet rendering flow is no longer passed through do_shortcode unsanitized.
  • If immediate patching is not possible:
    • Restrict or temporarily disable the public booking form until the plugin can be updated.
    • Monitor booking submissions for unusual content in name fields (e.g., bracketed shortcode syntax such as [...]).
    • Review Customer Cabinet / dashboard output for unexpected rendered content that may indicate a planted payload.
    • Enable a web application firewall rule to block shortcode-like patterns in booking form submissions as a stopgap measure.

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