JUNG eNet SMART HOME server 2.2.1 (46056)/2.3.1 (46841) HTTP POST Request /jsonrpc/management deleteUserAccount Username authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.8 | $0-$5k | 0.00 |
Summary
A vulnerability was found in JUNG eNet SMART HOME server 2.2.1 (46056)/2.3.1 (46841). It has been classified as problematic. This issue affects the function deleteUserAccount of the file /jsonrpc/management of the component HTTP POST Request Handler. This manipulation of the argument Username causes authorization.
This vulnerability is handled as CVE-2026-26367. The attack can be initiated remotely. There is not any exploit available.
Details
A vulnerability classified as problematic was found in JUNG eNet SMART HOME server 2.2.1 (46056)/2.3.1 (46841). Affected by this vulnerability is the function deleteUserAccount of the file /jsonrpc/management of the component HTTP POST Request Handler. The manipulation of the argument username with an unknown input leads to a authorization vulnerability. The CWE definition for the vulnerability is CWE-862. The product does not perform an authorization check when an actor attempts to access a resource or perform an action. As an impact it is known to affect availability. The summary by CVE is:
eNet SMART HOME server 2.2.1 and 2.3.1 contains a missing authorization vulnerability in the deleteUserAccount JSON-RPC method that permits any authenticated low-privileged user (UG_USER) to delete arbitrary user accounts, except for the built-in admin account. The application does not enforce role-based access control on this function, allowing a standard user to submit a crafted POST request to /jsonrpc/management specifying another username to have that account removed without elevated permissions or additional confirmation.
The weakness was released by Gjoko Krstic as ZSL-2026-5973. The advisory is shared at zeroscience.mk. This vulnerability is known as CVE-2026-26367 since 02/15/2026. The exploitation appears to be easy. The attack can be launched remotely. Technical details are known, but no exploit is available. The price for an exploit might be around USD $0-$5k at the moment (estimation calculated on 03/03/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-6143). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CNA CVSS-B Score: 🔒
CNA CVSS-BT Score: 🔒
CNA Vector: 🔒
CVSSv3
VulDB Meta Base Score: 6.8VulDB Meta Temp Score: 6.8
VulDB Base Score: 4.3
VulDB Temp Score: 4.2
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.1
NVD Vector: 🔒
CNA Base Score: 8.1
CNA Vector (VulnCheck): 🔒
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: AuthorizationCWE: CWE-862 / CWE-863 / CWE-285
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
02/15/2026 Advisory disclosed02/15/2026 CVE reserved
02/15/2026 VulDB entry created
03/03/2026 VulDB entry last update
Sources
Advisory: ZSL-2026-5973Researcher: Gjoko Krstic
Status: Not defined
CVE: CVE-2026-26367 (🔒)
GCVE (CVE): GCVE-0-2026-26367
GCVE (VulDB): GCVE-100-346141
EUVD: 🔒
Entry
Created: 02/15/2026 16:49Updated: 03/03/2026 05:21
Changes: 02/15/2026 16:49 (78), 02/19/2026 22:17 (1), 02/20/2026 06:06 (1), 02/27/2026 03:41 (11), 03/03/2026 05:21 (4)
Complete: 🔍
Cache ID: 216::103
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
No comments yet. Languages: en.
Please log in to comment.