CVE-2023-38052
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 /admins/{adminId} allows a low privileged user to fetch, modify or delete a high privileged user (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 (Broken Object Level Authorization) vulnerability in the /admins/{adminId} endpoint allows authenticated low-privileged users to perform GET, PUT, and DELETE operations on administrative accounts by manipulating the adminId parameter, 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 Easyappointments versionCheck the version.php file in the application root or examine the composer.json file for the installed versionAffected if The installed version is below 1.5.0
-
Verify API endpoint exposureLocate API routing configuration files (typically in a routes or api directory) and confirm the /admins/{adminId} endpoint is definedAffected if The endpoint exists and is routable without additional access controls documented in the codebase
-
Check authentication mechanismReview the authentication middleware or controller handling the /admins/{adminId} requests to confirm user authentication is required but authorization checks may be missingAffected if The endpoint accepts authenticated requests but lacks object-level authorization validation for the adminId parameter
-
Test low-privilege accessUsing a low-privileged authenticated user account, send GET/PUT/DELETE requests to /admins/{adminId} with a different admin's ID in the URL parameterAffected if The requests succeed and return administrative account data or allow modification/deletion without proper permission verification
A user is affected if Easyappointments version is below 1.5.0 and the /admins/{adminId} endpoint permits unauthorized access to administrative accounts by authenticated low-privileged 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 · scoped1.5.0
Implement and enforce object-level authorization checks at the API layer to verify the requesting user has permission to access, modify, or delete the specific admin resource before executing any operation.
Easyappointments 1.5.0
- 1. Backup your current Easyappointments installation and database
- 2. Download Easyappointments version 1.5.0 from the official GitHub repository or release channel
- 3. Replace the existing installation files with the new version 1.5.0 files
- 4. Run any database migration scripts included in the upgrade
- 5. Verify the application is functioning correctly
- 6. Test that the IDOR vulnerability is fixed by attempting unauthorized access to /admins/{adminId} endpoints with a low-privileged user account (this should now be denied)
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-2023-38052 — 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-38052 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