CVE-2023-3286
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 /secretaries allows a low privileged user to create a low privileged user (secretary) in the system. This results in 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 Broken Object Level Authorization (BOLA) vulnerability in the POST /secretaries endpoint allows any authenticated low-privileged user to create new secretary user accounts without proper authorization checks, resulting in unauthorized data manipulation.
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
- None
- Integrity
- High
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 installed Easyappointments versionLocate the version file (typically version.php in the root directory, or check composer.json/package.json for the version field). Compare the version number to the affected range: versions prior to 1.5.0 are vulnerable.Affected if The installed version is below 1.5.0
-
Confirm the /secretaries API endpoint existsLocate the API route definitions in the application (typically in routes.php or similar routing configuration files). Verify that a POST /secretaries endpoint is defined for creating secretary user accounts.Affected if The POST /secretaries endpoint is defined in the application routing
-
Check API endpoint authorization logicExamine the controller handling the POST /secretaries request. Look for authorization checks that verify the requesting user has sufficient privileges (such as admin-level access) before allowing creation of new secretary accounts.Affected if The endpoint lacks proper authorization checks or allows low-privileged authenticated users to create secretary accounts
You are affected if the installed Easyappointments version is below 1.5.0 and the POST /secretaries endpoint permits low-privileged users to create secretary accounts without proper authorization.
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 proper object-level authorization checks on the POST /secretaries endpoint to verify the requester has sufficient privileges to create new user accounts.
Easyappointments 1.5.0 or later
- Backup your current Easyappointments installation and database
- Download Easyappointments version 1.5.0 or later from the official GitHub repository (github.com/alextselegidis/easyappointments)
- Extract the new version and replace the application files on your server
- Verify file permissions are correctly set after the upgrade
- Test that the POST /secretaries endpoint properly enforces authorization (low-privileged users should no longer be able to create secretaries)
- Verify the application functions normally for all user roles
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-3286 — 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-3286 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