CVE-2026-120735latepoint Appointment Booking Plugin information exposure
CVE-2026-120735 is a information exposure in latepoint Appointment Booking Plugin, rated medium (5.3 on CVSS 3.1).
Why this priority: Medium severity, with no exploitation signal.
Published · Updated · NVD status: Deferred
What it is
The software reveals data to someone who should not see it.
How it is reached
An attacker can exploit it over the network, without an account, and nobody has to click anything.
What an attacker gains
The direct impact is limited: partial access to data or a partial outage. In practice, this kind of flaw lets an attacker learn data or internals that help a follow-up attack.
Is it being exploited?
There is no public report of exploitation yet.
What to do
- No fixed version is listed yet. Find every place latepoint Appointment Booking Plugin runs, watch the references for a fix, and plan a replacement if it is no longer supported.
- While there is no fix, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Description from NVD
The Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress plugin for WordPress is vulnerable to Sensitive Information Exposure in all versions up to, and including, 5.7.7 via the 'key' parameter. This makes it possible for unauthenticated attackers to extract full invoice and receipt records including customer full name, email address, phone number, invoice line items and totals, and the invoice's real access key. This is exploitable via the unauthenticated public routes invoices__view_by_key and transactions__view_receipt_by_key, which apply no ownership, capability, or nonce check before passing the attacker-supplied key into the ORM lookup.
What this means for your architecture.
A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.
Components it touches
- WordPress sites and their plugins. Plugins run inside the site with its database access, and many sites are public.
- Error responses, logs and debug endpoints. The flaw sits between internal data and whoever can read the response or log.
- APIs that over-share. The flaw sits between internal data and whoever can read the response or log.
Trust boundaries in play
- Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
- Between internal data and whoever can read the response or log. An attacker who crosses it can learn data or internals that help a follow-up attack.
Questions to answer about your own systems
- Where does latepoint Appointment Booking Plugin run in your systems, and at which version?
- Which of those instances can be reached from the internet or partner networks?
- What can it reach once compromised: which data stores, secrets and services?
Read more
Advisories
More reading
- plugins.trac.wordpress.org/browser/latepoint/tags/5.7.7/latepoint.php#L1076
- plugins.trac.wordpress.org/browser/latepoint/tags/5.7.7/lib/controllers/invoices_controller.php#L509
- plugins.trac.wordpress.org/browser/latepoint/tags/5.7.7/lib/controllers/transactions_controller.php#L54
- plugins.trac.wordpress.org/browser/latepoint/tags/5.7.7/lib/models/model.php#L452
- plugins.trac.wordpress.org/changeset/3781718/latepoint/trunk/lib/models/model.php
Sources
- CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
- Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
- Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
- Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.