CVE-2026-7457
Deferred Deferred - Pending Action
Stored Cross-Site Scripting in LatePoint WordPress Plugin

Publication date: 2026-05-06

Last updated on: 2026-05-06

Assigner: Wordfence

Description
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 (first_name, last_name, phone, notes) bypass sanitization because OsCustomerModel does not override params_to_sanitize(), causing set_data() to store unsanitized values verbatim in the database β€” combined with insufficient output escaping in generate_preview(), which injects those stored values into notification template HTML via str_replace() without any esc_html() 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 {{customer_full_name}}, {{customer_first_name}}, {{customer_last_name}}, {{customer_phone}}, or {{customer_notes}} is previewed.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-05-06
Last Modified
2026-05-06
Generated
2026-05-07
AI Q&A
2026-05-06
EPSS Evaluated
N/A
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
latepoint latepoint to 5.5.0 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-79 The product does not neutralize or incorrectly neutralizes user-controllable input before it is placed in output that is used as a web page that is served to other users.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

The LatePoint plugin for WordPress has a Stored Cross-Site Scripting (XSS) vulnerability in all versions up to and including 5.5.0. This occurs because the plugin does not properly sanitize input on the customer cabinet profile update endpoint. Specifically, raw POST parameters such as first_name, last_name, phone, and notes bypass sanitization due to the OsCustomerModel not overriding the params_to_sanitize() method. As a result, unsanitized data is stored directly in the database.

Additionally, when generating notification previews, the plugin injects these stored unsanitized values into HTML templates without escaping them properly. This allows authenticated users with customer-level access or higher to inject arbitrary scripts that execute in the browsers of administrators or agents when they preview notification templates referencing customer variables like {{customer_full_name}}, {{customer_first_name}}, {{customer_last_name}}, {{customer_phone}}, or {{customer_notes}}.


How can this vulnerability impact me? :

This vulnerability can allow an authenticated attacker with customer-level access to inject malicious scripts into the WordPress admin notification preview panel. These scripts execute in the browsers of administrators or agents, potentially leading to unauthorized actions such as session hijacking, data theft, or manipulation of the admin interface.


What immediate steps should I take to mitigate this vulnerability?

To mitigate this vulnerability, you should update the LatePoint plugin for WordPress to a version later than 5.5.0 where the issue is fixed.

Since the vulnerability arises from insufficient input sanitization and output escaping, avoid using the customer cabinet profile update endpoint to input untrusted data until patched.

Additionally, restrict customer-level access to trusted users only, as the exploit requires authenticated customer-level access or above.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart