Webkul QloApps up to 1.5.x id_order information disclosure
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.9 | $0-$5k | 0.00 |
Summary
A vulnerability was found in Webkul QloApps up to 1.5.x. It has been classified as problematic. Affected by this vulnerability is an unknown functionality. Performing a manipulation of the argument id_order results in information disclosure. This vulnerability is identified as CVE-2023-36235. There is not any exploit available. Upgrading the affected component is recommended.
Details
A vulnerability classified as problematic has been found in Webkul QloApps up to 1.5.x. This affects an unknown code block. The manipulation of the argument id_order with an unknown input leads to a information disclosure vulnerability. CWE is classifying the issue as CWE-200. The product exposes sensitive information to an actor that is not explicitly authorized to have access to that information. This is going to have an impact on confidentiality. The summary by CVE is:
An issue in webkul qloapps before v1.6.0 allows an attacker to obtain sensitive information via the id_order parameter.
The weakness was released 01/17/2024. The advisory is shared at github.com. This vulnerability is uniquely identified as CVE-2023-36235 since 06/21/2023. Technical details are known, but no exploit is available. MITRE ATT&CK project uses the attack technique T1592 for this issue.
Upgrading to version 1.6.0 eliminates this vulnerability. Applying a patch is able to eliminate this problem. The bugfix is ready for download at github.com. The best possible mitigation is suggested to be upgrading to the latest version.
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.0VulDB Meta Temp Score: 4.9
VulDB Base Score: 3.5
VulDB Temp Score: 3.4
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.5
NVD Vector: 🔍
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: Information disclosureCWE: CWE-200 / CWE-284 / CWE-266
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: UpgradeStatus: 🔍
0-Day Time: 🔍
Upgrade: QloApps 1.6.0
Patch: github.com
Timeline
06/21/2023 🔍01/17/2024 🔍
01/17/2024 🔍
06/10/2025 🔍
Sources
Advisory: github.comStatus: Confirmed
CVE: CVE-2023-36235 (🔍)
GCVE (CVE): GCVE-0-2023-36235
GCVE (VulDB): GCVE-100-251361
Entry
Created: 01/17/2024 09:34Updated: 06/10/2025 22:09
Changes: 01/17/2024 09:34 (41), 02/10/2024 15:55 (11), 06/10/2025 22:09 (16)
Complete: 🔍
Cache ID: 216::103
Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
No comments yet. Languages: en.
Please log in to comment.