dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7457

MEDIUM · 6.4 CVSS v3.1 Published 2026-05-06
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
70/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Stored XSS vulnerability in LatePoint WordPress plugin (versions up to 5.5.0) where customer profile fields (first_name, last_name, phone, notes) are stored without input sanitization because OsCustomerModel fails to override params_to_sanitize(), and output escaping is missing in generate_preview() when rendering notification template variables ({{customer_full_name}}, etc.) into HTML.

MitigationUpgrade LatePoint to version 5.5.1 or later which includes proper input sanitization in OsCustomerModel and output escaping in generate_preview(). Until patched, restrict customer account creation and review existing customer records for malicious content.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
Low
User interaction
None
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed LatePoint plugin version
    In WordPress admin, go to Plugins > Installed Plugins and find LatePoint, or check the version in the plugin's main file header (typically in wp-content/plugins/latepoint/latepoint.php)
    Affected if Version is 5.5.0 or lower (no version number displayed or lower than 5.5.1)
  2. Verify WordPress plugin is active
    Check if LatePoint appears in the active plugins list via Plugins admin page or by inspecting the wp_options table for 'active_plugins'
    Affected if Plugin is installed and active in WordPress
  3. Confirm customer account creation is accessible
    Check if the WordPress site allows customer registration or if LatePoint's customer creation functionality is enabled. Look for registration forms or customer dashboard features that accept first_name, last_name, phone, or notes fields
    Affected if Customer-facing forms that collect first_name, last_name, phone, or notes fields are accessible to users
  4. Check for existing notification templates using customer variables
    Locate notification templates in LatePoint settings (typically under Notifications or Templates) and inspect if they contain {{customer_full_name}}, {{customer_first_name}}, {{customer_last_name}}, {{customer_phone}}, or {{customer_notes}} placeholders
    Affected if Notification templates contain unescaped customer variable tags like {{customer_full_name}}

You are affected if LatePoint plugin version is 5.5.0 or earlier AND your site allows customer account creation or has notification templates using customer variable tags.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade LatePoint to version 5.5.1 or later which includes proper input sanitization in OsCustomerModel and output escaping in generate_preview(). Until patched, restrict customer account creation and review existing customer records for malicious content.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,750
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-7457 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-7457 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data