CVE-2026-4785
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 · uneditedThe LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to Stored Cross-Site Scripting via the 'button_caption' parameter in the [latepoint_resources] shortcode in versions up to and including 5.3.0. This is due to insufficient output escaping when the 'items' parameter is set to 'bundles'. This makes it possible for authenticated attackers, with contributor-level access and above, to inject arbitrary web scripts in pages that will execute whenever a user accesses an injected page.
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 confidenceThe LatePoint WordPress plugin up to 5.3.0 has a stored XSS vulnerability in the [latepoint_resources] shortcode. When the 'items' parameter is set to 'bundles', the 'button_caption' parameter is not properly escaped before output, allowing authenticated attackers with contributor-level access to inject malicious JavaScript that executes on page access.
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 checksWork through these to decide whether this CVE applies to you.
-
Confirm LatePoint plugin is installedIn WordPress admin, go to Plugins > Installed Plugins and verify the LatePoint plugin appears in the listAffected if The LatePoint plugin is not installed on the WordPress site
-
Identify the installed LatePoint versionIn WordPress admin, go to Plugins > Installed Plugins, find LatePoint, and note the version number displayedAffected if The installed version matches or precedes the unpatched version range for this CVE (compare your version to the vendor's advisory for the patched version)
-
Check for use of the [latepoint_resources] shortcodeSearch WordPress post/page content for the shortcode [latepoint_resources] using WP admin search or by querying the wp_posts tableAffected if The shortcode [latepoint_resources] with items='bundles' is present in any published content
-
Verify the items parameter is set to bundlesExamine any found [latepoint_resources] shortcode and confirm it contains items='bundles' or items="bundles"Affected if The shortcode includes items parameter set to bundles value
-
Inspect the button_caption parameterExamine the shortcode for a button_caption attribute (e.g., button_caption='Book Now') and check if user-supplied or untrusted input is used as its valueAffected if A button_caption parameter exists with arbitrary or untrusted content that may not have been sanitized through esc_html or esc_attr
The environment is affected if LatePoint plugin is installed with an unpatched version AND the [latepoint_resources] shortcode with items='bundles' is in use with a custom button_caption parameter containing potentially malicious content.
Generated from the published advisory. Verify against your own configuration.
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 dataUpgrade to version 5.3.1 or later which includes proper output escaping for the button_caption parameter, or implement immediate output escaping (esc_html/esc_attr) on the button_caption value in the shortcode handler.
- Consultation2.0 h
- Implementation3.0 h
- Testing3.0 h
- Review / QA2.0 h
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 locallyCheck whether your project pulls in CVE-2026-4785 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-4785 in production — separate from our analysis above.
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.
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.
- 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