Skip to content
Fencer Intel
critical 9.8

CVE-2023-34659 in the critical feed json

jeecg-boot SQL injection vulnerability

published 3y ago modified 4mo ago also GHSA-934g-fvcc-4833 , EUVD-2023-1756

cvss
9.8
version 3.1, NVD
cisa kev
Not listed
not in CISA's catalog
epss
12.5%
EPSS 12.5% chance of exploitation in 30 days, percentile 96%
public exploits
0
none known

Summary

jeecg-boot 3.5.0 and 3.5.1 have a SQL injection vulnerability the id parameter of the /jeecg-boot/jmreport/show interface.

Is CVE-2023-34659 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

CISA SSVC

Exploitation
Proof of concept is public
Automatable
yes
Technical impact
total
Assessed
last yr.

Exploit prediction

12.48% chance of exploitation in the next 30 days, higher than 96% of all scored CVEs (FIRST EPSS, 2026-11-15).

Exploits and checks

  • github.com https://github.com/jeecgboot/jeecg-boot/issues/4976 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-parent
>=3.5.0, <=3.5.1
no fix listed

Classification

Weakness
  • CWE-89 Improper Neutralization of Special Elements used in an SQL Command

References

Sources

Fencer Intel 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.