CVE-2026-119152 · Package
NO FIX YET · SEE WHAT TO DO
The LatePoint booking plugin for WordPress stores the customer email submitted on its public booking form without escaping it, so a crafted email address can carry an HTML payload. That payload runs in the browser of anyone who opens the page where it is rendered, including site administrators.
first public Nov 7, 2026 · 1 source
Check it with your coding agent
It checks your repository and tells you if you’re affected, with the fix.
Sites running the LatePoint plugin for WordPress up to and including 5.7.6 with the public booking form available to visitors. An attacker needs no WordPress account, since the booking flow creates a customer session. Sites that do not run LatePoint, or run a later version, are not affected.
Not affected if newer-than-5.7.6, plugin-not-installed
Who cares latepoint, self-hosted, wordpress
5.7.6.The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'customer[email] (inside params)' parameter in all versions up to, and including, 5.7.6 due to insufficient input sanitization and output escaping. This makes it possible for unauthenticated attackers to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page. An unauthenticated visitor can exploit this by registering as a LatePoint customer via the public booking form — receiving an active customer session with no WordPress account — and then submitting a quoted local-part email address containing an HTML payload (e.g. a tag with no spaces) that passes FILTER_VALIDATE_EMAIL but is stored and rendered unescaped.
This page as .md · .json · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:L/I:L/A:N
NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.
Are you affected?
Tell InfraStack what you run. It checks this one, and every next one, against your stack.
Ask from here. InfraStack checks the affected versions against your stack and answers in your inbox.
InfraStack checks the affected versions against your stack and answers in Slack, with the evidence and the fix.