CVE-2023-3288
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 /providers allows a low privileged user to create a privileged user (provider) 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 BOLA (Broken Object Level Authorization) vulnerability in the POST /providers API endpoint allows an authenticated low-privileged user to create privileged provider accounts, bypassing authorization controls and resulting in privilege escalation.
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 Easyappointments installation versionLocate the version file (commonly version.php, composer.json, or package.json in the application root) and read the version numberAffected if The installed version is any version prior to 1.5.0
-
Confirm the /providers API endpoint existsCheck the application routing configuration or API route definitions for the presence of a POST /providers endpointAffected if The endpoint is defined and accessible in the application routes
-
Verify API authentication is requiredSend an unauthenticated or low-privilege user request to POST /providers and observe the responseAffected if The endpoint accepts requests without proper authorization validation
-
Check authorization enforcement on provider creationUsing a low-privileged authenticated account, attempt a POST request to /providers to create a provider account and verify if the request succeedsAffected if A low-privileged user can successfully create a privileged provider account, bypassing authorization controls
The environment is affected if running Easyappointments version below 1.5.0 and the POST /providers endpoint permits low-privileged authenticated users to create privileged provider accounts without proper authorization validation.
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 authorization checks on the POST /providers endpoint to verify the requesting user has sufficient privileges before allowing provider account creation.
1.5.0
- 1. Back up your current Easyappointments installation and database
- 2. Download Easyappointments version 1.5.0 from the official GitHub repository (github.com/alextselegidis/easyappointments)
- 3. Replace the existing installation files with the new version 1.5.0 files
- 4. Run any database migrations if required (check the release notes for migration scripts)
- 5. Verify that the application functions correctly after the upgrade
- 6. Test that low-privileged users can no longer create privileged provider accounts via POST /providers endpoint
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-3288 — 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-3288 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