Skip to main content
CVE-2024-48307VulnerabilityPublished

CVE-2024-48307: JeecgBoot · n/a

Affects JeecgBootSource CVE Database V5

0

Not known to be exploited · public detection template (Nuclei) · 50% EPSS · CVSS 9.8 Critical.

Data as of 25 Oct 2026, 19:02 UTC

CVSS 3.1 base score
9.8Critical
How severe the flaw is on the 0–10 CVSS scale.
EPSS
50.0% chance of exploitation in 30 days – higher than 98% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 31 Oct 2024

  2. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  3. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  4. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 2026-10-25.

What to do

Affected software

ProductAffectedFixed in
GitHubjeecgboot/JeecgBootpkg:github/jeecgboot/JeecgBootOther threatsAffected
  • =3.7.1
Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

1. Immediately identify all instances of JeecgBoot version 3.7.1 in your environment and restrict external access to the /onlDragDatasetHead/getTotalData endpoint until patched. 2. Apply any official patches or updates from JeecgBoot developers as soon as they become available. 3. Implement strict input validation and parameterized queries or prepared statements in the affected component to prevent SQL injection. 4. Deploy Web Application Firewalls (WAFs) with rules targeting SQL injection patterns, especially for the vulnerable endpoint. 5. Conduct thorough code reviews and security testing focusing on database query handling in JeecgBoot applications. 6. Monitor logs for unusual database queries or error messages indicative of injection attempts. 7. Limit database user privileges to the minimum necessary to reduce potential damage from exploitation. 8. Educate development teams on secure coding practices to prevent similar vulnerabilities in future releases. 9. Consider network segmentation to isolate critical systems and reduce attack surface. 10. Prepare incident response plans specific to SQL injection attacks to enable rapid containment and recovery.

Description

JeecgBoot v3.7.1 was discovered to contain a SQL injection vulnerability via the component /onlDragDatasetHead/getTotalData.

References

Community reviews

Loading reviews…