Quick answers
- Is CVE-2025-50383 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2025-50383 being exploited in the wild.
- How severe is CVE-2025-50383?
- High severity, with a CVSS score of 8.1, published 25 August 2025.
- Which products and versions are affected?
- alextselegidis/easyappointments (Packagist) ECOSYSTEM:introduced=0,fixed=1.5.2-beta.1.
- Is there a fix for CVE-2025-50383?
- Yes. alextselegidis/easyappointments (Packagist): upgrade to 1.5.2-beta.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2025-50383 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2025-50383?
- Check whether you run alextselegidis/easyappointments (Packagist) 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.
How to fix
- alextselegidis/easyappointments (Packagist): upgrade to 1.5.2-beta.1 or later
composer require alextselegidis/easyappointments:^1.5.2-beta.1
Technical details
A SQL injection vulnerability exists in Easy!Appointments v1.5.1 due to improper neutralization of the 'order_by' parameter in several backend search endpoints. Low-privileged authenticated users (such as Customers and Providers) can exploit this via the /customers/search, /Unavailabilities/search, and /Appointments/search endpoints by submitting a crafted HTTP POST request. The vulnerability manifests as a time-based blind SQL injection (e.g., using SLEEP commands), allowing an attacker to extract data from the underlying MySQL database. Administrative endpoints are also affected but require higher privileges. The issue is resolved in version 1.5.2.
Affected products
- alextselegidis Easy!Appointments 1.5.1
Identifiers
- CVE-2025-50383
- GHSA-2f28-69j7-85hf
Timeline
- 2025-08-25: disclosed
- 2025-08-25: advisory
- 2025-08-25: patched: Fixed in version 1.5.2