# CVE-2026-2519: Online Scheduling and Appointment Booking System – Bookly <= 27.0 - Unauthenticated Price Manipulation via 'tips'

> Unauthenticated attackers can manipulate booking prices to zero by submitting negative tips, requiring plugin updates to enforce server-side validation.

- **Severity:** Medium 5.3 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 9 Apr 2026
- **Updated:** 13 Apr 2026
- **Also known as:** GHSA-ghp2-h9w4-7r66

## What is CVE-2026-2519?

CVE-2026-2519 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

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.

Weakness: CWE-472 (External Control of Assumed-Immutable Web Parameter)

## Which versions are affected by CVE-2026-2519?


## How do I fix CVE-2026-2519?

No fix has been published for CVE-2026-2519 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-2519 being exploited?

There is no known exploitation of CVE-2026-2519 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-2519 and fix it if it is affected.

What it is: CVE-2026-2519 is a medium-severity vulnerability in ladela Online Scheduling and Appointment Booking System – Bookly, published on 9 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-2519 in the wild and no public exploit code.

Affected product: ladela Online Scheduling and Appointment Booking System – Bookly. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-2519/ (Markdown: https://insights.sbomify.com/CVE-2026-2519/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-2519
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-2519
- OSV: https://osv.dev/vulnerability/CVE-2026-2519

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-2519/
Summaries are generated and may contain mistakes; the official description above is the record.