Skip to content
Patch Next
Sign inAdd to your agent

← Actionable
Medium, CVSS 6.9amended

Easy!Appointments has unauthenticated customer PII disclosure on booking reschedule page

CVE-2026-52837GHSA-xgr6-pqjv-3pf8

What to do

Vendor response not established. Follow the primary source's mitigation guidance and check back for a fix.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Add to your agent

Affected packages

  • Packagist alextselegidis/easyappointments

    Affected
    <= 1.5.2
    Fixed in
    no fixed version recorded

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS 4.0
6.9 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N · score source
EPSS
  • CVE-2026-52837: 0.46% estimated exploitation activity in the next 30 days; percentile 39.86 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Summary The booking reschedule view at /index.php/booking/reschedule/{appointmenthash} (handled by Booking::index()) embeds the entire customer record as inline JavaScript (const vars = {... "customerdata": {...}, ...}) without authentication and without field whitelisting. Anyone in possession of the 12-character appointmenthash — which appears in plain text in reschedule emails, confirmation page URLs, and operator-side calendar links — can read every column of that customer's row in the eausers table. Verified against v1.5.2 with a Docker reproduction; a single anonymous GET to the reschedule URL returns 13 customer fields including email, phone, full address, custom fields, timezone, language, LDAP DN, and idroles. Details Root cause application/controllers/Booking.php at line 184 reads the hash from the request, fetches the appointment, then loads the customer with Customersmodel::find() — which returns the full row, no projection. It then passes the full record into…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 3 · amended ·

    Amended from ghsa record GHSA-xgr6-pqjv-3pf8

  2. Revision 2 · amended ·

    Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

  3. Revision 1 · created ·

    Published from osv record GHSA-xgr6-pqjv-3pf8

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-52837

Advisory: Easy!Appointments has unauthenticated customer PII disclosure on booking reschedule page
IDs: CVE-2026-52837, GHSA-xgr6-pqjv-3pf8
Record: https://patchnext.com/advisories/cve-2026-52837 (revision 3, source checked 26 Oct 2026, 14:50 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.9)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor response not established. A vendor fix does not mean a deployment is fixed.

## Affected components
- Packagist alextselegidis/easyappointments: affected <= 1.5.2

## Suggested inspection (read-only)
- Packagist alextselegidis/easyappointments: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on alextselegidis/easyappointments.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-xgr6-pqjv-3pf8 (OSV record GHSA-xgr6-pqjv-3pf8 lists affected ranges: Packagist alextselegidis/easyappointments >=0 <=1.5.2)
- Verified: https://github.com/advisories/GHSA-xgr6-pqjv-3pf8 (GitHub-reviewed advisory GHSA-xgr6-pqjv-3pf8 lists affected ranges: Packagist alextselegidis/easyappointments >=0 <=1.5.2)

Commands are suggestions: review each one before running it.

Loading voting…