CVE-2023-3287
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 POST /admins allows a low privileged user to create a high privileged user (admin) in the system. This results in privilege escalation.
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 Broken Object Level Authorization (BOLA) vulnerability in the POST /admins endpoint allows any authenticated low-privilege user to create high-privileged admin accounts by bypassing role-based access controls on the user creation function.
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
- High
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
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 versionLocate the version file or version definition in the Easyappointments installation directory (commonly found in version.php, composer.json, or a config/version file within the application root)Affected if The version is lower than 1.5.0
-
Verify the /admins endpoint existsInspect the application routing configuration or source code to confirm the POST /admins endpoint is defined and accessibleAffected if The endpoint exists and is reachable without proper role validation in the routing/Controller code
-
Check for role-based authorization on admin creationReview the source code handling the POST /admins request to determine if role verification (checking if the requester is an admin) occurs before processing the requestAffected if No role check or an insufficient role check is performed before allowing admin account creation
-
Test low-privilege user access to admin creationUsing a low-privilege authenticated user account, attempt to send a POST request to /admins to create an admin-level accountAffected if The low-privilege user can successfully create an admin account without receiving a 403 Forbidden or authorization error
You are affected if Easyappointments version is below 1.5.0 and the POST /admins endpoint allows low-privilege authenticated users to create admin accounts without proper authorization checks.
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 proper authorization checks to verify the requester's role before allowing admin account creation; enforce role validation on all administrative endpoints.
Easyappointments 1.5.0
- 1. Back up your existing Easyappointments database and files before proceeding with the upgrade.
- 2. Download Easyappointments version 1.5.0 or later from the official repository (github.com/alextselegidis/easyappointments).
- 3. Replace the existing application files with the new version files, preserving your configuration file (typically config.php) and any customizations.
- 4. Verify that the application functions correctly by logging in and testing the admin user creation functionality.
- 5. Confirm that low-privileged users can no longer create admin-level users through the POST /admins endpoint.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3287 — 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-3287 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