dbcve.org
EasyappointmentsApplication

CVE-2023-38049

HIGH · 8.1 CVSS v3.1 Published 2024-07-09
Fix available
A fix is available. Upgrade to 1.5.0 or later.
See remediation →
87/100
Remediation priority · High
Remotely reachable Zero-click

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 · unedited
A BOLA vulnerability in GET, PUT, DELETE /appointments/{appointmentId} allows a low privileged user to fetch, modify or delete an appointment of any user (including admin). This results in unauthorized access and unauthorized data manipulation.

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 confidence

A BOLA (Broken Object Level Authorization) vulnerability in the GET, PUT, and DELETE /appointments/{appointmentId} endpoints allows authenticated low-privileged users to access, modify, or delete appointments belonging to any user, including administrators. The application fails to verify that the requesting user owns or has permission to access the specific appointment resource before returning or modifying data.

MitigationImplement and enforce object-level authorization checks on all appointment endpoints to verify the authenticated user has explicit permission to access, modify, or delete the requested appointment resource, regardless of the user's privilege level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
EasyappointmentsApplication
Affected:< 1.5.0

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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify Easyappointments version
    Check the installed version of Easyappointments by examining the version file, composer.json, or the application's about/settings page. Common paths include /version.php, /composer.json in the web root, or through the admin dashboard.
    Affected if The installed version is below 1.5.0 (e.g., 1.4.x, 1.3.x, etc.)
  2. Confirm API endpoint availability
    Verify the REST API is accessible by checking if the /appointments endpoint exists. This may be found at paths like /api/v1/appointments or /index.php/api/v1/appointments depending on the installation.
    Affected if The /appointments API endpoints are exposed and accessible in the application
  3. Check API authorization configuration
    Examine the API configuration files (typically in /application/config/ or similar) to see if authorization middleware exists for the appointments endpoints. Look for files handling API authentication and authorization logic.
    Affected if No explicit object-level ownership verification exists in the API endpoint handlers for appointment resources
  4. Verify user role handling in appointments
    Review the appointment controller code (usually in /application/controllers/ or /api/controllers/) to confirm whether the code verifies that the authenticated user owns the appointment before allowing GET, PUT, or DELETE operations.
    Affected if The code does not verify appointment ownership before returning or modifying data for the requested appointmentId

A user is affected if they run Easyappointments version below 1.5.0 and the application exposes the appointments API endpoint without proper ownership verification for appointment resources.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 1.5.0 or later
Fixed in 1.5.0
Interim mitigation

Implement and enforce object-level authorization checks on all appointment endpoints to verify the authenticated user has explicit permission to access, modify, or delete the requested appointment resource, regardless of the user's privilege level.

Recommended fix High confidence

Easyappointments 1.5.0 or later

  1. 1. Backup the Easyappointments database and files before any changes
  2. 2. Download Easyappointments version 1.5.0 or later from the official GitHub repository (github.com/alextselegidis/easyappointments)
  3. 3. Replace existing application files with the new version, preserving configuration (config.php) and any custom assets
  4. 4. Run database migrations if included in the upgrade (check for migrate scripts in the repository)
  5. 5. Clear any application caches
  6. 6. Test that authorization controls now properly restrict appointment access - verify a low-privileged user can no longer access appointments belonging to other users via direct API calls
Caveat Review release notes for 1.5.0 to check for breaking changes in API, plugins, or custom integrations; test thoroughly in a staging environment before production deployment

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Easyappointments Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,040.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-38049 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-38049 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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