CVE-2023-3290
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 /customers allows a low privileged user to create a low privileged user (customer) 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 BOLA (Broken Object Level Authorization) vulnerability in the POST /customers endpoint allows authenticated low-privileged users to create new customer accounts without proper authorization checks. The system fails to validate whether the requesting user has permission to create new customer records, 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
- Changed
- Confidentiality
- None
- Integrity
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:C/C:N/I:L/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 is installedLocate the Easyappointments installation directory or check for its characteristic file structure (index.php, config.php, and the /customers API endpoint).Affected if The application is Easyappointments and is reachable via web browser or API client.
-
Identify the installed versionCheck the version file, config.php, or any version information file in the Easyappointments installation directory. Compare the version number against the affected range: < 1.5.0.Affected if The installed version is earlier than 1.5.0.
-
Verify the POST /customers endpoint existsConfirm the /customers endpoint is available by checking the API route definitions in the application source code (typically in a routes or API configuration file).Affected if The POST /customers endpoint is present in the application.
-
Check user role configuration for customer creationExamine the user role permissions configuration to determine which roles have permission to create customer records. Look for role-based access control (RBAC) settings in the database or config files.Affected if Low-privileged user roles (such as regular users or limited staff) are configured with permission to access the POST /customers endpoint.
-
Test endpoint authorization (if authorized)Using a low-privileged authenticated user account, send a POST request to /customers and verify if the request is processed without returning an authorization error.Affected if The request succeeds and a new customer record is created, indicating the authorization check is missing or ineffective.
The environment is affected if Easyappointments version is below 1.5.0 and low-privileged users can successfully create customer records via POST /customers 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 proper object-level authorization checks on the POST /customers endpoint to verify the requesting user has sufficient privileges to create customer records. Enforce authorization validation before processing the request.
Easyappointments 1.5.0
- Download Easyappointments version 1.5.0 from the official repository or release page
- Backup your existing database and application files before upgrading
- Replace the existing application files with the new version 1.5.0 files
- Run any database migrations if included in the upgrade
- Verify that the application functions correctly after the upgrade
- Confirm that low-privileged users can no longer create additional user accounts via the /customers endpoint
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-3290 — 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-3290 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