JeecgBoot 3.9.0 Online Report API loadDictItemByKeyword keyword sql injection
Summary
A vulnerability was found in JeecgBoot 3.9.0. It has been classified as critical. This issue affects some unknown processing of the file /JeecgBoot/sys/api/loadDictItemByKeyword of the component Online Report API. Performing a manipulation of the argument keyword results in sql injection. This vulnerability is reported as CVE-2026-1746. The attack is possible to be carried out remotely. Moreover, an exploit is present. The vendor was contacted early about this disclosure but did not respond in any way.
Details
A vulnerability, which was classified as critical, was found in JeecgBoot 3.9.0. This affects an unknown code block of the file /JeecgBoot/sys/api/loadDictItemByKeyword of the component Online Report API. The manipulation of the argument keyword with an unknown input leads to a sql injection vulnerability. CWE is classifying the issue as CWE-89. The product constructs all or part of an SQL command using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify the intended SQL command when it is sent to a downstream component. This is going to have an impact on confidentiality, integrity, and availability.
The advisory is shared at yuque.com. This vulnerability is uniquely identified as CVE-2026-1746. The exploitability is told to be easy. It is possible to initiate the attack remotely. Technical details and a public exploit are known. MITRE ATT&CK project uses the attack technique T1505 for this issue.
The exploit is shared for download at yuque.com. It is declared as proof-of-concept. The vendor was contacted early about this disclosure but did not respond in any way.
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-5095). If you want to get the best quality for vulnerability data then you always have to consider VulDB.
Product
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: 7.1VulDB Meta Temp Score: 6.9
VulDB Base Score: 6.3
VulDB Temp Score: 5.7
VulDB Vector: 🔒
VulDB Reliability: 🔍
NVD Base Score: 8.8
NVD Vector: 🔒
CNA Base Score: 6.3
CNA 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: Sql injectionCWE: CWE-89 / CWE-74 / CWE-707
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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/01/2026 Advisory disclosed02/01/2026 VulDB entry created
02/11/2026 VulDB entry last update
Sources
Advisory: yuque.comStatus: Not defined
CVE: CVE-2026-1746 (🔒)
GCVE (CVE): GCVE-0-2026-1746
GCVE (VulDB): GCVE-100-343677
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 02/01/2026 06:17 PMUpdated: 02/11/2026 04:44 AM
Changes: 02/01/2026 06:17 PM (56), 02/02/2026 07:23 AM (30), 02/03/2026 05:57 AM (1), 02/11/2026 04:44 AM (11)
Complete: 🔍
Submitter: jjcc20220820
Cache ID: 244::40
Submit
Accepted
- Submit #741647: Beijing Guoju Information Technology Co., Ltd JeecgBoot 3.9.0 SQL Injection (by jjcc20220820)
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.