Steedos Platform up to 3.0.15-beta.51 ObjectQL Call Adapter /api/v1/reports find/findOne authorization
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.3 | $0-$5k | 2.51+ |
Summary
A vulnerability classified as problematic has been found in Steedos Platform up to 3.0.15-beta.51. This vulnerability affects the function find/findOne of the file /api/v1/reports of the component ObjectQL Call Adapter. Performing a manipulation results in authorization.
This vulnerability was named CVE-2026-111666. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability was found in Steedos Platform up to 3.0.15-beta.51. It has been classified as problematic. This affects the function find/findOne of the file /api/v1/reports of the component ObjectQL Call Adapter. The manipulation with an unknown input leads to a authorization vulnerability. CWE is classifying the issue as CWE-639. The system's authorization functionality does not prevent one user from gaining access to another user's data or record by modifying the key value identifying the data. This is going to have an impact on confidentiality. The summary by CVE is:
Steedos Platform through 3.0.15-beta.51 contains an authorization bypass vulnerability that allows authenticated users to read other tenants' report definitions by querying the reports object. Because objectql's callAdapter skips space filtering for enable_space_global objects on find/findOne, attackers can call GET /api/v1/reports to disclose report names, descriptions, and object and field API names.
The advisory is shared at hackmd.io. This vulnerability is uniquely identified as CVE-2026-111666 since 10/16/2026. The exploitability is told to be easy. It is possible to initiate the attack 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 10/16/2026).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
Name
Version
- 3.0.15-beta.0
- 3.0.15-beta.1
- 3.0.15-beta.2
- 3.0.15-beta.3
- 3.0.15-beta.4
- 3.0.15-beta.5
- 3.0.15-beta.6
- 3.0.15-beta.7
- 3.0.15-beta.8
- 3.0.15-beta.9
- 3.0.15-beta.10
- 3.0.15-beta.11
- 3.0.15-beta.12
- 3.0.15-beta.13
- 3.0.15-beta.14
- 3.0.15-beta.15
- 3.0.15-beta.16
- 3.0.15-beta.17
- 3.0.15-beta.18
- 3.0.15-beta.19
- 3.0.15-beta.20
- 3.0.15-beta.21
- 3.0.15-beta.22
- 3.0.15-beta.23
- 3.0.15-beta.24
- 3.0.15-beta.25
- 3.0.15-beta.26
- 3.0.15-beta.27
- 3.0.15-beta.28
- 3.0.15-beta.29
- 3.0.15-beta.30
- 3.0.15-beta.31
- 3.0.15-beta.32
- 3.0.15-beta.33
- 3.0.15-beta.34
- 3.0.15-beta.35
- 3.0.15-beta.36
- 3.0.15-beta.37
- 3.0.15-beta.38
- 3.0.15-beta.39
- 3.0.15-beta.40
- 3.0.15-beta.41
- 3.0.15-beta.42
- 3.0.15-beta.43
- 3.0.15-beta.44
- 3.0.15-beta.45
- 3.0.15-beta.46
- 3.0.15-beta.47
- 3.0.15-beta.48
- 3.0.15-beta.49
- 3.0.15-beta.50
- 3.0.15-beta.51
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: 4.3VulDB Meta Temp Score: 4.3
VulDB Base Score: 4.3
VulDB Temp Score: 4.3
VulDB Vector: 🔒
VulDB Reliability: 🔍
CNA Base Score: 4.3
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-639 / CWE-285 / CWE-266
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
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/16/2026 Advisory disclosed10/16/2026 CVE reserved
10/16/2026 VulDB entry created
10/16/2026 VulDB entry last update
Sources
Advisory: hackmd.ioStatus: Not defined
CVE: CVE-2026-111666 (🔒)
GCVE (CVE): GCVE-0-2026-111666
GCVE (VulDB): GCVE-100-421413
Entry
Created: 10/16/2026 20:34Changes: 10/16/2026 20:34 (74)
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.