CVE-2026-11398 json
LatePoint <= 5.6.1 - Missing Authorization to Unauthenticated Arbitrary Customer Data Modification via process_step_customer() Booking Form Customer Step
published 4mo ago modified 4mo ago also EUVD-2026-41524
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.6%
- EPSS 0.6% chance of exploitation in 30 days, percentile 46%
- public exploits
- 0
- none known
Summary
The LatePoint – Calendar Booking Plugin for Appointments and Events plugin for WordPress is vulnerable to authorization bypass in all versions up to, and including, 5.6.1. This is due to the plugin not properly verifying that a user is authorized to perform an action. This makes it possible for unauthenticated attackers to modify the personally identifiable information (first name, last name, phone number, and notes) of any existing customer record, including those linked to administrator accounts, by submitting the booking form with a known customer's email address. Exploitation requires the plugin to be configured with guest bookings enabled (is_customer_auth_disabled() returning true), which is necessary for the vulnerable unauthenticated code path in process_step_customer() to be reached.
Is CVE-2026-11398 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
- 4mo ago
Exploit prediction
0.56% chance of exploitation in the next 30 days, higher than 46% of all scored CVEs (FIRST EPSS, 2026-11-09).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 5.3 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N |
Affected products
- latepoint LatePoint – Calendar Booking Plugin for Appointments and Events
Classification
- Weakness
-
- CWE-862 Missing Authorization
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/e4dcedcc-2878-47b2-99f0-ecba2cc33b69?source=cve
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.1/lib/helpers/steps_helper.php#L1980
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.1/lib/helpers/steps_helper.php#L1953
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.1/lib/helpers/steps_helper.php#L1892
- plugins.trac.wordpress.org /browser/latepoint/tags/5.6.1/lib/controllers/steps_controller.php#L22
- plugins.trac.wordpress.org /browser/latepoint/tags/5.3.2/lib/helpers/steps_helper.php#L1980
- plugins.trac.wordpress.org /browser/latepoint/tags/5.3.2/lib/helpers/steps_helper.php#L1953
- plugins.trac.wordpress.org /browser/latepoint/tags/5.3.2/lib/helpers/steps_helper.php#L1892
- plugins.trac.wordpress.org /browser/latepoint/tags/5.3.2/lib/controllers/steps_controller.php#L22
- plugins.trac.wordpress.org /changeset?sfp_email=&sfph_mail=&reponame=&old=3572632%40latepoint&new=3572632%40latepoint&sfp_email=&sfph_mai
Sources
- CVE List CVE-2026-11398
- NVD CVE-2026-11398
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.