CVE-2023-38992 in the critical feed json
SQL injection in jeecg-boot
published 2023-07-28 3 y ago modified 2026-06-17 4 mo ago also GHSA-wp6c-29r3-jqw9 , EUVD-2023-2169
- cvss
- 9.8
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 73.4%
- EPSS 73.4% chance of exploitation in 30 days, percentile 99.4%
- public exploits
- 0
- none known, plus a Nuclei check
Summary
jeecg-boot v3.5.1 was discovered to contain a SQL injection vulnerability via the title parameter at /sys/dict/loadTreeData.
Patch / fix
- maven org.jeecgframework.boot:jeecg-boot-common 3.5.3
CISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- yes
- Technical impact
- total
- Assessed
- 2 y ago
Exploit prediction
73.40% chance of exploitation in the next 30 days, higher than 99.4% of all scored CVEs (FIRST EPSS, 2026-11-08).
Exploits and checks
- Nuclei template Jeecg-Boot v3.5.1 - SQL Injection nuclei detection template
- github.com https://github.com/jeecgboot/jeecg-boot/issues/5173 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
| GitHub | 3.1 | 9.8 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| maven | org.jeecgframework.boot:jeecg-boot-common | <3.5.3 |
3.5.3 |
Classification
- Weakness
-
- CWE-89 Improper Neutralization of Special Elements used in an SQL Command
References
-
github.com
/jeecgboot/jeecg-boot/issues/5173
web, exploit, issue-tracking, patch
-
github.com
/jeecgboot/jeecg-boot/commit/648e66d5ef1547a01ff77bf9875f960ca39bbe8e
web
-
nvd.nist.gov
/vuln/detail/CVE-2023-38992
advisory
-
github.com
/jeecgboot/jeecg-boot-starter
package
Sources
- CVE List CVE-2023-38992
- GitHub Advisory GHSA-wp6c-29r3-jqw9
- NVD CVE-2023-38992
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.