CVE-2023-38048
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 · uneditedA BOLA vulnerability in GET, PUT, DELETE /providers/{providerId} allows a low privileged user to fetch, modify or delete a privileged user (provider). 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 confidenceA BOLA (Broken Object Level Authorization) vulnerability in the GET, PUT, and DELETE /providers/{providerId} endpoints allows a low-privileged user to fetch, modify, or delete a privileged provider account by manipulating the providerId parameter in the request URL, bypassing proper authorization checks.
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< 1.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify the installed Easyappointments versionCheck the version.php file in the application root directory, or look for a version identifier in the admin dashboard under System Information or About sectionAffected if The installed version is earlier than 1.5.0 (e.g., 1.4.x, 1.3.x, etc.)
-
Confirm the providers API endpoints are accessibleAttempt to access the /providers endpoint base path via HTTP request to verify the REST API is enabled and respondingAffected if The API returns HTTP 200 or other valid responses indicating the endpoint exists and is reachable
-
Verify if low-privileged users can enumerate provider IDsLog in with a low-privilege user account and send GET requests to /providers/{providerId} using different providerId values (numeric IDs)Affected if A low-privileged user can successfully retrieve details of provider accounts they should not have access to
-
Test unauthorized modification via PUT endpointUsing a low-privilege user session, send a PUT request to /providers/{providerId} with a providerId belonging to a different/privileged userAffected if The request succeeds and modifies provider data that belongs to another user without authorization check failure
-
Test unauthorized deletion via DELETE endpointUsing a low-privilege user session, send a DELETE request to /providers/{providerId} targeting a providerId belonging to a privileged accountAffected if The provider account is deleted successfully or the request does not return an authorization error
A user is affected if running Easyappointments version below 1.5.0 AND the API responds to /providers/{providerId} requests without properly validating that the authenticated user owns or has permission to access the specified provider resource.
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 · scoped1.5.0
Implement and enforce object-level authorization checks on all provider endpoints to verify the authenticated user has permission to access/modify/delete the specific provider resource before processing the request.
Easyappointments 1.5.0
- 1. Back up the current Easyappointments installation directory and database before attempting any upgrade
- 2. Download Easyappointments version 1.5.0 from the official GitHub repository (github.com/alextselegidis/easyappointments)
- 3. Replace the existing Easyappointments installation files with version 1.5.0 files, preserving configuration and any custom assets
- 4. Test the upgrade in a non-production environment to verify the fix works and no regressions are introduced
- 5. After successful testing, deploy version 1.5.0 to production
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing4.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 $4,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-38048 — 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-2023-38048 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