Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2026-7332

HIGH · 7.2 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 →

81/100

Remediation priority · High

Remotely reachable No privileges Zero-click

Official description

NVD · unedited

The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'booking_form_page_url' parameter in all versions up to, and including, 5.5.0 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. The malicious activity log entry is written to the database even when Stripe is not configured, because the latepoint_order_intent_created action hook fires before the Stripe Connect account ID is validated, meaning a fully functional Stripe integration is not required for exploitation.

Technical summary

dbcve analysis · high confidence

The LatePoint WordPress plugin fails to sanitize the 'booking_form_page_url' parameter and escape it on output, allowing stored XSS injection. Additionally, the plugin writes malicious activity log entries before validating the Stripe Connect account ID, meaning exploitation requires no Stripe configuration and can be triggered by unauthenticated users.

MitigationApply vendor patch when available; until then, consider restricting the plugin or adding WAF rules to block requests with suspicious 'booking_form_page_url' values.

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

CVSS breakdown

From the vector

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

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

Am I affected?

dbcve checks

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

Confirm LatePoint plugin is installed

In WordPress admin, go to Plugins > Installed Plugins and verify the LatePoint plugin is present and active

Affected if LatePoint plugin is installed and active
Identify installed LatePoint version

In WordPress admin, go to Plugins > Installed Plugins, find LatePoint, and note the version number displayed

Affected if Version is unpatched (no fixed version specified in CVE; compare against vendor advisories)
Verify booking form functionality is exposed

Check if the WordPress site has booking forms publicly accessible (look for frontend booking pages or shortcodes like [latepoint_booking_form])

Affected if Booking form pages are publicly accessible without authentication
Inspect request handling for booking_form_page_url

Submit a test booking form submission with a crafted booking_form_page_url parameter containing a benign test payload (e.g., <script>alert(1)</script>) and verify it gets stored in the database without sanitization

Affected if The parameter value is stored and displayed without HTML encoding/sanitization in admin logs or frontend output

A user is affected if LatePoint plugin is installed, the booking form is publicly accessible, and the booking_form_page_url parameter accepts and stores unsanitized input that gets rendered without escaping

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

Remediation

dbcve · scoped

Mitigation available No clean upgrade yet — mitigate in the meantime

Mitigation

Apply vendor patch when available; until then, consider restricting the plugin or adding WAF rules to block requests with suspicious 'booking_form_page_url' values.

Recommended fix Moderate confidence

Latest version of LatePoint plugin (beyond 5.5.0)

Navigate to the WordPress admin dashboard
Go to Plugins > Installed Plugins
Find the LatePoint – Calendar Booking Plugin for Appointments and Events
Check if an update is available and update to the latest version

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory

Consultation2.0 h
Implementation4.0 h
Testing3.0 h
Review / QA2.0 h

11.0 hours of engineering $1,930

Get help mitigating

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

Scan for this in your stack

Free · runs locally

dbcve dependency scanner

Check whether your project pulls in CVE-2026-7332 — 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

Primary sources

Practitioner notes

Contributed

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

Notes0 Guidelines

Know something about CVE-2026-7332?

The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.

The version that genuinely resolved it — not the one the vendor claimed
A config change or rule that shut the vector down
A gotcha in the upgrade path that cost you an afternoon

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

At a glance

A fix existsA vendor remedy is published

Severity 7.2 High

Exploit likelihood EPSS, next 30 days 0.5%

Remediation

A high-priority fix

Have this fixed 11 hrs · Moderate

Typical engagement from $1,930

Get a fix See the full breakdown ↓

A high-priority vulnerability. Send your environment and a specialist will scope CVE-2026-7332 and return a fixed quote and timeline.

You’ll deal with our team directly and deploy the reviewed fix to staging first — never straight to production.

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.

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.

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.

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.

Check your environment

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.

Scan for this in your stack

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

Practitioner notes

No notes yet

Official description

Technical summary

CVSS breakdown

Am I affected?

Remediation

References