CVE-2023-3289
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 /services allows a low privileged user to create a service for any user in the system (including admin). 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 BOLA (Broken Object Level Authorization) vulnerability in the POST /services endpoint allows any authenticated user to create services on behalf of other users, including administrators. The API fails to validate whether the requesting user has permission to create services for the specified target user, enabling 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.
-
Confirm Easyappointments installationLocate the Easyappointments application in your environment - typically deployed as a web application with typical Easyappointments file structure and brandingAffected if Easyappointments is present in the environment
-
Determine installed versionCheck the application version against the affected range. Typical version locations include a version file, composer.json, or the admin dashboard. Compare your version to the threshold of 1.5.0Affected if Installed version is lower than 1.5.0
-
Verify API endpoint accessibilityConfirm the REST API is accessible at the /services endpoint. Typically this is found at /api/v1/services or similar API route depending on installation configurationAffected if The POST /services API endpoint is accessible and responds to requests
-
Test authorization on POST /servicesSend an authenticated API request to POST /services with a target user identifier different from the authenticated user. Examine whether the API accepts the request without validating that the authenticated user has permission to act on behalf of the target userAffected if The API allows creating services for a user other than the authenticated user without proper authorization validation
You are affected if Easyappointments version is below 1.5.0 and the POST /services endpoint permits authenticated users to create services for other users without 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 at the API layer to verify the authenticated user has explicit permission to create services for the specified target user. Enforce strict validation that users can only create services for themselves unless explicitly authorized.
Easyappointments 1.5.0
- 1. Back up your current Easyappointments installation and database before proceeding.
- 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 and customizations.
- 4. Run any database migrations if required by the upgrade.
- 5. Verify that the application functions correctly after the upgrade.
- 6. Test that low-privileged users can no longer create services for other users (including admins).
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-3289 — 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-3289 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