LatePoint <= 5.3.2 - Authenticated (Contributor+) Stored Cross-Site Scripting via Shortcode Attributes

6.4
Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE CVE-2026-5391
CVSS 6.4 (Medium)
Publicly Published August 5, 2026
Last Updated August 6, 2026
Researcher alex_henry20

Description

The LatePoint plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'btn_wrapper_classes' attribute of the 'latepoint_resources' shortcode in all versions up to, and including, 5.3.2. This is due to insufficient input sanitization and output escaping in the 'locations' branch of the 'shortcode_latepoint_resources' function. This makes it possible for authenticated attackers, with contributor level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.

Learn more about Cross-Site Scripting vulnerabilities and how to prevent them.

References

Share

Vulnerability Details for Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

Software Type Plugin
Software Slug latepoint (view on wordpress.org)
Patched? Yes
Remediation Update to version 5.4.0, or a newer patched version
Affected Version
  • <= 5.3.2
Patched Version
  • 5.4.0

Recent vulnerabilities in Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress

# Title CVE ID CVSS Researchers Date
1 Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress <= 5.6.9 - Authenticated (Subscriber+) Insecure Direct Object Reference to Arbitrary Customer PII Modification CVE-2026-17538 5.4 owlmind October 7, 2026
2 Appointment Booking Plugin <= 5.7.1 - Insecure Direct Object Reference to Unauthenticated Unauthorized Transaction Intent Creation/Modification and Invoice Enumeration via 'invoice_id' Parameter CVE-2026-94432 5.3 Niv Kochan, Matan Bachar October 1, 2026
3 Appointment Booking Plugin <= 5.7.0 - Unauthenticated Arbitrary Shortcode Execution via First/Last Name Field CVE-2026-92966 9.1 hashiramasenju333 September 30, 2026
4 LatePoint <= 5.6.3 - Authenticated (Custom+) Insecure Direct Object Reference to Arbitrary Booking Deletion and Customer/Booking Data Disclosure via Abilities REST API (list-bookings, list-customers, delete-booking) CVE-2026-13471 4.3 skyv3il, Chirita Catalin-Andrei (CC99IE), AmonRa, MrProperCTF September 17, 2026
5 LatePoint - Appointment Booking & Scheduling <= 5.6.9 - Unauthenticated Insecure Direct Object Reference to Sensitive Information Disclosure via 'customer[id]' Parameter CVE-2026-18441 4.3 Sorra September 17, 2026
6 LatePoint <= 5.6.7 - Missing Authorization to Unauthenticated Booking Object Mass Assignment CVE-2026-15250 5.3 Revanth Hari Narayana Matte July 10, 2026
7 Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress <= 5.6.3 - Unauthenticated SQL Injection CVE-2026-57714 7.5 daroo July 8, 2026
8 LatePoint - Calendar Booking Plugin for Appointments and Events <= 5.4.0 - Unauthenticated Stripe PaymentIntent Amount-Binding Bypass CVE-2026-5356 7.5 Andrés Cruciani July 7, 2026
9 LatePoint <= 5.6.1 - Missing Authorization to Unauthenticated Arbitrary Customer Data Modification via process_step_customer() Booking Form Customer Step CVE-2026-11398 5.3 hhhai July 2, 2026
10 LatePoint <= 5.6.2 - Unauthenticated Insecure Direct Object Reference to Arbitrary Creation via 'service_id' Parameter CVE-2026-12657 5.3 gidget smith July 1, 2026

Did you know Wordfence Intelligence provides free personal and commercial API access to our comprehensive WordPress vulnerability database, along with a free webhook integration to stay on top of the latest vulnerabilities added and updated in the database? Get started today!

Learn more

Want to get notified of the latest vulnerabilities that may affect your WordPress site?
Install Wordfence on your site today to get notified immediately if your site is affected by a vulnerability that has been added to our database.

Get Wordfence

The Wordfence Intelligence WordPress vulnerability database is completely free to access and query via API. Please review the documentation on how to access and consume the vulnerability data via API.

Documentation