Quick answers
- Is CVE-2026-109525 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-109525 being exploited in the wild.
- How severe is CVE-2026-109525?
- High severity, with a CVSS score of 7.3, published 13 October 2026.
- Which products and versions are affected?
- Girishsaraf Online-Appointment-Booking-System up to commit f427b4757128ca253d33d0cc4e87bbb9c999a4d5.
- Is there a fix for CVE-2026-109525?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-109525 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-109525?
- Check whether you run Girishsaraf Online-Appointment-Booking-System at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
The changebookingstatus.php file's submit2 handler accepts username[], timestamp[], and status[] POST parameters without verifying that the requester is authenticated or authorized to modify appointments. An attacker can craft a POST request with arbitrary username and timestamp values to change any booking's status without credentials. The vulnerable code directly uses unsanitized POST data in SQL queries to update the book table.
Affected products
- girishsaraf Online-Appointment-Booking-System up to commit f427b4757128ca253d33d0cc4e87bbb9c999a4d5
Timeline
- 2026-09-16: disclosed
- 2026-10-13: advisory
- other: Exploit is publicly available