Skip to main content
VulnerabilityPublished

CVE-2026-119152: Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress · Cross-site Scripting

Affects Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPressSource CVE Database V5

0
Compare

Not known to be exploited · CVSS 5.4 Medium.

Data as of 7 Nov 2026, 02:50 UTC

CVSS 3.1 base score
5.4Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Wordfence)CVSS 3.15.4
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 7 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 6 Nov 2026.

What to do

Affected software

ProductAffectedFixed in
latepointAppointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPressAffected
  • <=5.7.6
Fixed in–

AI-suggested

Users should monitor the vendor's advisories for updates. Until a fix is available, restricting access to the booking form or implementing additional input validation and output escaping at the application or web server level may reduce risk. Avoid using affected versions in production environments where possible.

Description

The Appointment Booking Plugin – LatePoint for WordPress up to version 5.7.6 is vulnerable to a stored cross-site scripting (XSS) flaw via the 'customer[email]' parameter. This vulnerability allows unauthenticated attackers to inject malicious scripts by submitting a crafted email address through the public booking form, which is stored and rendered without proper escaping. Exploitation requires the attacker to register as a customer, gaining an active session without a WordPress account. The vulnerability arises from insufficient input sanitization and output escaping of the email parameter.

References

Community reviews

Loading reviews…