CVE-2026-2519 json
Online Scheduling and Appointment Booking System – Bookly <= 27.0 - Unauthenticated Price Manipulation via 'tips'
published 2026-04-09 7 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-20890
- cvss
- 5.3
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.5%
- EPSS 0.5% chance of exploitation in 30 days, percentile 40%
- public exploits
- 0
- none known
Summary
The Online Scheduling and Appointment Booking System – Bookly plugin for WordPress is vulnerable to price manipulation via the 'tips' parameter in all versions up to, and including, 27.0. This is due to the plugin trusting a user-supplied input without server-side validation against the configured price. This makes it possible for unauthenticated attackers to submit a negative number to the 'tips' parameter, causing the total price to be reduced to zero.
CISA SSVC
- Exploitation
- none
- Automatable
- yes
- Technical impact
- partial
- Assessed
- 6 mo ago
Exploit prediction
0.47% chance of exploitation in the next 30 days, higher than 40% of all scored CVEs (FIRST EPSS, 2026-11-08).
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
- ladela Online Scheduling and Appointment Booking System – Bookly
Classification
- Weakness
-
- CWE-472 External Control of Assumed-Immutable Web Parameter
- Technology feeds
References
- wordfence.com /threat-intel/vulnerabilities/id/ead87d8b-2659-4e8b-a0b9-138b1db89e36?source=cve
- plugins.trac.wordpress.org /browser/bookly-responsive-appointment-booking-tool/trunk/lib/UserBookingData.php#L355
- plugins.trac.wordpress.org /browser/bookly-responsive-appointment-booking-tool/trunk/frontend/modules/booking/Ajax.php#L709
- plugins.trac.wordpress.org /browser/bookly-responsive-appointment-booking-tool/trunk/lib/CartInfo.php#L450
- plugins.trac.wordpress.org /changeset/3480956/
- booking-wp-plugin.com /change-log/
Sources
- CVE List CVE-2026-2519
- NVD CVE-2026-2519
Fencer Vulns 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.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.