CVE-2026-55651
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedEasy!Appointments is a self hosted appointment scheduler. In version 1.5.2, an Excessive Data Exposure vulnerability in the customers search endpoint allows an authenticated user to obtain appointment hashes belonging to other users. Using these hashes, an attacker can modify or delete appointments of other providers, resulting in an Appointments Takeover. Version 1.6.0 fixes the issue.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceEasy!Appointments 1.5.2 contains an Excessive Data Exposure vulnerability in the customers search endpoint that returns appointment hashes belonging to other authenticated users. An attacker with valid credentials can retrieve these hashes and use them to modify or delete appointments of other providers, achieving full appointment takeover.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:H/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify Easy!Appointments installationLocate the Easy!Appointments application files. Common paths include /var/www/html/easyappointments, /www/easyappointments, or check your web server document root for an 'easyappointments' directory containing index.phpAffected if Easy!Appointments software is present in the environment
-
Check installed versionOpen the file 'application/config/config.php' or 'includes/version.php' in the Easy!Appointments directory and look for a version definition (e.g., defined('EA_VERSION') or similar)Affected if The version returned is 1.5.2 exactly or falls within the 1.5.x range prior to 1.6.0
-
Verify customers endpoint existsCheck for the presence of the customers controller file at 'application/controllers/Customers.php' and verify the search method is definedAffected if The customers search endpoint exists and is accessible via /index.php/customers/search or similar URL pattern
-
Confirm authentication is enabledCheck 'application/config/config.php' for $config['enable_auth'] = true; or verify user authentication is not disabled in the installationAffected if User authentication is enabled, allowing authenticated users to access the customers search endpoint
You are affected if Easy!Appointments version 1.5.2 is installed with authentication enabled and the customers search endpoint is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade to Easy!Appointments version 1.6.0 or later, which addresses the authorization flaw in the customers search endpoint to prevent cross-user data exposure.
1.6.0
- Back up the current Easy!Appointments installation and database before proceeding with the upgrade
- Download Easy!Appointments version 1.6.0 from the official repository
- Replace the existing installation files with the new version 1.6.0 files
- Run any database migrations or setup scripts included in version 1.6.0
- Verify that the customers search endpoint no longer exposes appointment hashes belonging to other users
- Test that users can only access their own appointments
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-55651 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-55651 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data