Jeebase 0.0.1 UserService /user/update/info updateUser user/tempUser dynamically-determined object attributes
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.0 | $0-$5k | 2.23- |
Summary
A vulnerability marked as critical has been reported in Jeebase 0.0.1. This issue affects the function updateUser of the file /user/update/info of the component UserService. The manipulation of the argument user/tempUser leads to dynamically-determined object attributes.
This vulnerability is uniquely identified as CVE-2026-105180. The attack is possible to be carried out remotely. Moreover, an exploit is present.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability, which was classified as critical, has been found in Jeebase 0.0.1. This issue affects the function updateUser of the file /user/update/info of the component UserService. The manipulation of the argument user/tempUser with an unknown input leads to a dynamically-determined object attributes vulnerability. Using CWE to declare the problem leads to CWE-915. The product receives input from an upstream component that specifies multiple attributes, properties, or fields that are to be initialized or updated in an object, but it does not properly control which attributes can be modified. Impacted is confidentiality, integrity, and availability.
The advisory is shared at github.com. The identification of this vulnerability is CVE-2026-105180. The exploitation is known to be easy. The attack may be initiated remotely. Technical details as well as a public exploit are known.
The exploit is available at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.0
VulDB Base Score: 6.3
VulDB Temp Score: 6.0
VulDB Vector: 🔒
VulDB Reliability: 🔍
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: Dynamically-determined object attributesCWE: CWE-915 / CWE-913
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
10/04/2026 Advisory disclosed10/04/2026 VulDB entry created
10/04/2026 VulDB entry last update
Sources
Advisory: 88Status: Confirmed
CVE: CVE-2026-105180 (🔒)
GCVE (CVE): GCVE-0-2026-105180
GCVE (VulDB): GCVE-100-413417
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 10/04/2026 11:27Changes: 10/04/2026 11:27 (58)
Complete: 🔍
Submitter: mjh_456
Cache ID: 216::103
Submit
Accepted
- Submit #971178: Jeebase 0.0.1 Mass Assignment (by mjh_456)
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.