CVE-2023-38055
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 /services/{serviceId} allows a low privileged user to fetch, modify or delete the services 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 confidenceA BOLA vulnerability in the /services/{serviceId} endpoint allows authenticated users to access, modify or delete services belonging to other users by manipulating the serviceId parameter. The endpoint fails to verify that the requesting user owns or has permission to access the specified service before returning or modifying data.
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.
-
Determine installed Easyappointments versionLocate the version file in the Easyappointments installation directory (typically version.php, composer.json, or package.json) and read the version numberAffected if the version is below 1.5.0 (e.g., 1.4.x, 1.3.x, etc.)
-
Verify /services API endpoint existsLocate the API routes configuration or Services controller file in the application directory and confirm the /services/{serviceId} endpoint is definedAffected if the endpoint exists and is accessible via HTTP methods (GET, PUT, DELETE)
-
Confirm authentication is required for the endpointInspect the Services controller or API middleware configuration to verify that user authentication is enforced before allowing access to the /services/{serviceId} endpointAffected if authentication is enabled but the endpoint does not verify the authenticated user owns the requested service
-
Check for ownership verification in the endpoint logicExamine the Services controller code handling GET, PUT, and DELETE requests to /services/{serviceId} - look for code that validates the requesting user's ID matches the service's owner before returning or modifying dataAffected if the endpoint processes requests without validating that the authenticated user has permission to access the specified serviceId
You are affected if you are running Easyappointments version below 1.5.0 AND the /services/{serviceId} endpoint is accessible to authenticated users without proper ownership verification.
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 authorization checks to verify the authenticated user has permission to access or modify the specific service before performing any GET, PUT, or DELETE operation on /services/{serviceId}.
Easyappointments 1.5.0 or later
- 1. Backup your current Easyappointments installation and database before upgrading
- 2. Download Easyappointments version 1.5.0 from the official repository or release page
- 3. Upgrade your existing installation to version 1.5.0 following the standard upgrade procedure
- 4. After upgrade, verify that low-privileged users can no longer access services belonging to other users via the /services/{serviceId} endpoint
- 5. Test that the authorization controls properly enforce access restrictions on GET, PUT, and DELETE operations for services
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-38055 — 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-38055 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