CVE-2026-103380 json
Appointment Booking Plugin <= 5.7.3 - Authenticated (Subscriber+) Sensitive Information Exposure in 'first_name' Parameter Template Re-expansion
published 26d ago modified 25d ago also EUVD-2026-100902
- cvss
- 4.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 24%
- public exploits
- 0
- none known
Summary
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.3 via the 'params[customer][first_name]' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to extract privileged booking data including the administrator-only admin_notes field, assigned agent internal contact details, transaction tokens, and payment request URLs delivered via rendered notification emails. A LatePoint customer can exploit this by storing a template placeholder such as {{customer_admin_notes}} in their own first_name field via the customer_cabinet__update route, then triggering the password-reset email flow to receive the expanded value in the resulting notification.
Is CVE-2026-103380 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 25d ago
Exploit prediction
0.31% chance of exploitation in the next 30 days, higher than 24% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 4.3 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N |
Affected products
- latepoint Appointment Booking Plugin – LatePoint | Calendar & Scheduling for WordPress
Classification
- Weakness
-
- CWE-200 Exposure of Sensitive Information to an Unauthorized Actor
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/4494960c-66ed-47d9-b3fc-5a5ec5a07b1f?source=cve
- plugins.trac.wordpress.org /browser/latepoint/tags/5.7.3/lib/helpers/replacer_helper.php#L278
- plugins.trac.wordpress.org /browser/latepoint/tags/5.7.3/lib/helpers/replacer_helper.php#L614
- plugins.trac.wordpress.org /browser/latepoint/tags/5.7.3/lib/controllers/customer_cabinet_controller.php#L321
- plugins.trac.wordpress.org /browser/latepoint/tags/5.7.3/lib/models/customer_model.php#L388
- plugins.trac.wordpress.org /browser/latepoint/tags/5.7.3/lib/mailers/customer_mailer.php#L33
- plugins.trac.wordpress.org /changeset?reponame=&old=3728691%40latepoint&new=3728691%40latepoint
Sources
- CVE List CVE-2026-103380
- NVD CVE-2026-103380
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.