Quick answers
- Is CVE-2026-52839 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-52839 being exploited in the wild.
- How severe is CVE-2026-52839?
- Low severity, with a CVSS score of 3.3, published 14 July 2026.
- Which products and versions are affected?
- alextselegidis/easyappointments (Packagist) <= 1.5.2, ECOSYSTEM:introduced=0,fixed=1.6.0.
- Is there a fix for CVE-2026-52839?
- Yes. alextselegidis/easyappointments (Packagist): upgrade to 1.6.0 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-52839 attacked?
- It is attacked over the network, in a network appliance.
- Am I affected by CVE-2026-52839?
- 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.6.0 or later
composer require alextselegidis/easyappointments:^1.6.0
Technical details
The vulnerability exists in the `appointments/store` and `appointments/update` endpoints of Easy!Appointments. While the application correctly filters search results by provider, these mutation endpoints only verify generic 'add' or 'edit' permissions and fail to validate that the `id_users_provider` field matches the authenticated user's session. An attacker with provider-level privileges can submit a crafted JSON payload to inject new appointments into another provider's schedule or reassign existing ones. Additionally, the `store` endpoint contains a 'write-before-crash' bug where the unauthorized record is committed to the database before a type error causes a 500 response, potentially masking the successful exploit. The issue is fixed in version 1.6.0.
Affected products
- alextselegidis Easy!Appointments <= 1.5.2
Identifiers
- CVE-2026-52839
- GHSA-w8xc-8g92-v77h
Timeline
- 2026-05-25: disclosed: Vulnerability reported by Yash Shendge
- 2026-06-15: patched: Version 1.6.0 released
- 2026-07-14: advisory: NVD publication date
- 2026-07-29: advisory: GitHub Advisory published