WeBankPartners WeCube 3.2.2 Resources/System Params/Basekey Configuration csv injection
CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
---|---|---|
6.3 | $0-$5k | 0.00 |
Summary
A vulnerability has been found in WeBankPartners WeCube 3.2.2 and classified as critical. This vulnerability affects unknown code of the component Resources/System Params/Basekey Configuration. The manipulation leads to csv injection. This vulnerability was named CVE-2022-37786. The attack can be initiated remotely. There is no exploit available. Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Details
A vulnerability, which was classified as critical, was found in WeBankPartners WeCube 3.2.2 (Banking Software). This affects an unknown functionality of the component Resources/System Params/Basekey Configuration. The manipulation with an unknown input leads to a csv injection vulnerability. CWE is classifying the issue as CWE-1236. The product saves user-provided information into a Comma-Separated Value (CSV) file, but it does not neutralize or incorrectly neutralizes special elements that could be interpreted as a command when the file is opened by a spreadsheet product. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
An issue was discovered in WeCube Platform 3.2.2. There are multiple CSV injection issues: the [Home / Admin / Resources] page, the [Home / Admin / System Params] page, and the [Home / Design / Basekey Configuration] page.
The weakness was published 01/01/2023 as 2327. It is possible to read the advisory at github.com. This vulnerability is uniquely identified as CVE-2022-37786 since 08/08/2022. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 04/11/2025).
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔍VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.3
VulDB Base Score: 6.3
VulDB Temp Score: 6.3
VulDB Vector: 🔍
VulDB Reliability: 🔍
NVD Base Score: 6.3
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: Csv injectionCWE: CWE-1236 / CWE-74 / CWE-707
CAPEC: 🔍
ATT&CK: 🔍
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
08/08/2022 🔍01/01/2023 🔍
01/01/2023 🔍
04/11/2025 🔍
Sources
Advisory: 2327Status: Confirmed
CVE: CVE-2022-37786 (🔍)
GCVE (CVE): GCVE-0-2022-37786
GCVE (VulDB): GCVE-100-217155
Entry
Created: 01/01/2023 12:26Updated: 04/11/2025 16:34
Changes: 01/01/2023 12:26 (39), 01/01/2023 14:11 (1), 01/26/2023 16:14 (9), 04/11/2025 16:34 (16)
Complete: 🔍
Cache ID: 216:411:103
No comments yet. Languages: en.
Please log in to comment.