CVE-2023-38992

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.8 under NVD CVSS v3. EPSS exploit probability: 64.1%, top 2% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, nvd
Weaponized
9.8
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 72%
CISA-KEV: Not listedEPSS: 72%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

jeecg-boot v3.5.1 was discovered to contain a SQL injection vulnerability via the title parameter at /sys/dict/loadTreeData.

CVSS v3
9.8
EG Score
9.8(medium)
EPSS
99.4%
KEV
Not listed

Published

July 28, 2023

Last Modified

November 21, 2024

Advisory Details (1)

Auto-updated May 27, 2026
No patch confirmed yet.
generic

SQL注入 · Issue #5173 · jeecgboot/JeecgBoot · GitHub

https://github.com/jeecgboot/jeecg-boot/issues/5173

Affected Packages

(1 across 1 ecosystem)
Maven(1)
PackageVulnerable rangeFixed inDependents
org.jeecgframework.boot:jeecg-boot-common3.4.0 ... 3.5.2 (7 versions)3.5.3

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 5× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-12 05:45 UTCEPSS rescore
  2. 2026-07-11 08:26 UTCEPSS rescore
  3. 2026-07-11 08:25 UTCEPSS rescore
  4. 2026-07-09 19:08 UTCEPSS rescore
  5. 2026-07-09 19:08 UTCEPSS rescore
  6. 2026-07-04 06:29 UTCEPSS rescore
  7. 2026-07-01 15:04 UTCEPSS rescore
  8. 2026-06-28 14:06 UTCEPSS rescore
  9. 2026-06-28 14:06 UTCEPSS rescore
  10. 2026-06-28 04:55 UTCEPSS rescore
  11. 2026-06-28 04:55 UTCEPSS rescore
  12. 2026-06-27 14:34 UTCOSV refresh
  13. 2026-06-25 13:48 UTCEPSS rescore
  14. 2026-06-25 13:48 UTCEPSS rescore
  15. 2026-06-23 21:31 UTCEPSS rescore
  16. 2026-06-23 21:31 UTCEPSS rescore
  17. 2026-06-21 01:58 UTCEPSS rescore
  18. 2026-06-21 01:58 UTCEPSS rescore
  19. 2026-06-18 17:51 UTCEPSS rescore
  20. 2026-06-18 17:51 UTCEPSS rescore
  21. 2026-06-17 17:51 UTCEPSS rescore
  22. 2026-06-17 17:51 UTCEPSS rescore
  23. 2026-06-16 17:51 UTCEPSS rescore
  24. 2026-06-16 17:51 UTCEPSS rescore
  25. 2026-06-15 17:47 UTCEPSS rescore
Show 30 more
  1. 2026-06-13 22:59 UTCEPSS rescore
  2. 2026-06-13 22:59 UTCEPSS rescore
  3. 2026-06-12 23:10 UTCEPSS rescore
  4. 2026-06-12 23:10 UTCEPSS rescore
  5. 2026-06-11 13:59 UTCEPSS rescore
  6. 2026-06-11 13:59 UTCEPSS rescore
  7. 2026-06-10 22:17 UTCEPSS rescore
  8. 2026-06-10 13:21 UTCEPSS rescore
  9. 2026-06-10 01:17 UTCOSV refresh
  10. 2026-06-07 15:23 UTCEPSS rescore
  11. 2026-06-07 15:23 UTCEPSS rescore
  12. 2026-06-05 22:46 UTCEPSS rescore
  13. 2026-06-05 22:46 UTCEPSS rescore
  14. 2026-06-05 06:09 UTCEPSS rescore
  15. 2026-06-05 06:09 UTCEPSS rescore
  16. 2026-06-04 13:11 UTCEPSS rescore
  17. 2026-06-04 13:11 UTCEPSS rescore
  18. 2026-06-02 20:12 UTCEPSS rescore
  19. 2026-06-02 20:12 UTCEPSS rescore
  20. 2026-06-02 20:12 UTCEPSS rescore
  21. 2026-06-01 13:51 UTCEPSS rescore
  22. 2026-06-01 13:51 UTCEPSS rescore
  23. 2026-05-29 13:43 UTCEPSS rescore
  24. 2026-05-29 13:43 UTCEPSS rescore
  25. 2026-05-28 13:43 UTCEPSS rescore
  26. 2026-05-28 13:43 UTCEPSS rescore
  27. 2026-05-27 13:39 UTCEPSS rescore
  28. 2026-05-26 13:43 UTCEPSS rescore
  29. 2026-05-26 13:43 UTCEPSS rescore
  30. 2026-05-24 20:29 UTCEG score recompute

Publicly available exploits

(1 reference)

Working exploit code is in the public domain. Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Nucleihttp/cves/2023/CVE-2023-38992.yaml
    First seen Jan 1, 2023

    Jeecg-Boot v3.5.1 - SQL Injection

    Open source ↗

Frequently asked(5)

What is CVE-2023-38992?
CVE-2023-38992 is a critical vulnerability published on July 28, 2023. jeecg-boot v3.5.1 was discovered to contain a SQL injection vulnerability via the title parameter at /sys/dict/loadTreeData.
When was CVE-2023-38992 disclosed?
CVE-2023-38992 was first published in the National Vulnerability Database on July 28, 2023, with the most recent update on November 21, 2024. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2023-38992 actively exploited?
CVE-2023-38992 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 99.4% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2023-38992?
CVE-2023-38992 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2023-38992?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2023-38992, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2023-38992

Explore →

Is Your Infrastructure Affected by CVE-2023-38992?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.