CVE-2026-7457: LatePoint <= 5.5.0 - Authenticated (Subscriber+) Stored Cross-Site Scripting via Customer Cabinet Profile Update
The LatePoint plugin for WordPress is vulnerable to Stored Cross-Site Scripting in all versions up to and including 5.5.0. This is due to insufficient input sanitization on the customer cabinet profile update endpoint — where raw POST parameters (firstname, lastname, phone, notes) bypass sanitization because OsCustomerModel does not override paramstosanitize(), causing setdata() to store unsanitized values verbatim in the database — combined with insufficient output escaping in generatepreview(), which injects those stored values into notification template HTML via strreplace() without any eschtml() call before echoing the result. This makes it possible for authenticated attackers with customer-level access or above to inject arbitrary web scripts into the admin notification preview panel that execute in an administrator's or agent's browser whenever a notification template referencing customer variables such as {{customerfullname}}, {{customerfirstname}}, {{customerlastname}}, {{customerphone}}, or {{customernotes}} is previewed.
Affected Software
Event History
Frequently Asked Questions
What is the severity of CVE-2026-7457?
CVE-2026-7457 is considered high severity due to its potential for stored cross-site scripting attacks.
How do I fix CVE-2026-7457?
To fix CVE-2026-7457, update the LatePoint WordPress plugin to version 5.5.1 or later.
What is the exploit type of CVE-2026-7457?
CVE-2026-7457 is a stored cross-site scripting vulnerability.
Who is affected by CVE-2026-7457?
All users of the LatePoint WordPress plugin versions up to and including 5.5.0 are affected by CVE-2026-7457.
What are the potential impacts of CVE-2026-7457?
The potential impacts of CVE-2026-7457 include unauthorized access to user data and malware injection via cross-site scripting.