CVE-2023-1750
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 · uneditedThe listed versions of Nexx Smart Home devices lack proper access control when executing actions. An attacker with a valid NexxHome deviceId could retrieve device history, set device settings, and retrieve device information.
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 · moderate confidenceNexx Smart Home devices suffer from broken access control where the API accepts a valid deviceId but fails to verify the requester is authorized to access that specific device. An attacker with any valid deviceId can read device history, retrieve device information, and modify device settings without proper ownership verification.
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<= nxal100v-p1-9-1<= nxg100bv-p3-4-1<= nxpg100cv4-0-0<= nxg200v-p3-4-1CVSS 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
- Low
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/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.
-
Identify your Nexx device modelLocate the physical device or check your device documentation/app to determine if it is one of the following models: Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200Affected if The device is any of these four models
-
Check the installed firmware versionAccess the device settings through the Nexx smart home mobile application or web interface and locate the firmware version information. Compare it against the affected version thresholds: Nxal 100 <= nxal100v-p1-9-1, Nxg 100b <= nxg100bv-p3-4-1, Nxpg 100w <= nxpg100cv4-0-0, Nxg 200 <= nxg200v-p3-4-1Affected if The firmware version is at or below the specified threshold for your device model
-
Verify API authorization behaviorUsing the Nexx API (typically accessible at the device's network endpoint or through the cloud service), attempt to access device data or control endpoints using a valid deviceId that you did not create or do not own. Observe whether the API returns data or allows changes without rejecting the request due to unauthorized ownershipAffected if The API returns device information, history, or allows setting modifications for a deviceId that does not belong to the authenticated user
-
Confirm proper device ownership validation existsReview API responses when making requests with valid authentication tokens but with deviceId parameters for devices not associated with your account. Check for proper 401/403 error responses indicating authorization failureAffected if The API fails to return 401/403 errors and instead provides access to devices outside your ownership
You are affected if you own a Getnexx Nxal 100, Nxg 100b, Nxpg 100w, or Nxg 200 device running firmware at or below the specified version thresholds and the API does not validate that the authenticated user owns the requested deviceId before returning data or accepting changes.
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.
From vendor dataImplement proper authorization checks validating that the authenticated user owns or has permission for the requested deviceId before returning data or accepting setting changes. Consider adding token-based authentication with device ownership validation.
- Consultation6.0 h
- Implementation16.0 h
- Testing8.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 $9,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-1750 — 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-1750 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