Skip to main content
VulnerabilityPublished

CVE-2026-5391: 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 6.4 Medium.

Data as of 5 Nov 2026, 23:24 UTC

CVSS 3.1 base score
6.4Medium
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 17% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 6 Aug 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 5 Nov 2026.

What to do

Affected software

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

AI-suggested

Until an official fix is available, restrict contributor-level access and above to trusted users only. Monitor for updates from the LatePoint plugin vendor regarding patches or official mitigations.

Description

The LatePoint Appointment Booking Plugin for WordPress contains a stored cross-site scripting (XSS) vulnerability in the 'btn_wrapper_classes' attribute of the 'latepoint_resources' shortcode. This vulnerability affects all versions up to and including 5.3.2 and allows authenticated users with contributor-level access or higher to inject arbitrary scripts that execute when a page is viewed. The issue arises from insufficient input sanitization and output escaping in the 'locations' branch of the shortcode processing function.

References

Community reviews

Loading reviews…