CVE-2026-26369
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 · uneditedeNet SMART HOME server 2.2.1 and 2.3.1 contains a privilege escalation vulnerability due to insufficient authorization checks in the setUserGroup JSON-RPC method. A low-privileged user (UG_USER) can send a crafted POST request to /jsonrpc/management specifying their own username to elevate their account to the UG_ADMIN group, bypassing intended access controls and gaining administrative capabilities such as modifying device configurations, network settings, and other smart home system functions.
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 confidenceThe eNet SMART HOME server versions 2.2.1 and 2.3.1 contain a privilege escalation vulnerability in the setUserGroup JSON-RPC method. This method lacks proper server-side authorization validation, allowing an authenticated low-privileged user (UG_USER) to craft a POST request to /jsonrpc/management specifying their own username and manually setting their group to UG_ADMIN, thereby gaining full administrative capabilities over the smart home system.
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= 2.2.1= 2.3.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
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/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 installed Enet Smart Home versionLocate the application or check the service banner responding on the management interface port (typically 80/443). Compare the version number to 2.2.1 or 2.3.1.Affected if The installed version is exactly 2.2.1 or 2.3.1.
-
Confirm /jsonrpc/management endpoint is accessibleSend an HTTP GET or POST request to /jsonrpc/management on the server. A successful response (even an error indicating method not found) indicates the endpoint is exposed.Affected if The /jsonrpc/management endpoint responds to requests, meaning it is network-accessible.
-
Verify setUserGroup method is exposedSend a JSON-RPC request to /jsonrpc/management with method setUserGroup. Check if the method is recognized (look for method not found or similar response indicating the method exists).Affected if The setUserGroup method is available and responds, indicating it has not been removed or disabled.
-
Test if low-privileged users can invoke setUserGroupAuthenticate as a UG_USER account and send a POST request to /jsonrpc/management with a payload attempting to change your own group to UG_ADMIN. Observe whether the request is accepted or rejected.Affected if The request succeeds or is processed without proper authorization rejection, allowing a UG_USER to call setUserGroup.
You are affected if you run version 2.2.1 or 2.3.1 of Jung Group Enet Smart Home and the /jsonrpc/management endpoint with the setUserGroup method is accessible to low-privileged users.
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 server-side authorization checks in the setUserGroup method to verify the requesting user has UG_ADMIN privileges before allowing any group modifications; consider upgrading to a patched version when available.
- 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-2026-26369 — 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-2026-26369 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