dbcve.org
Jeecg BootApplication · Jeecg

CVE-2024-43028

CRITICAL · 9.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 3.5.3 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A command injection vulnerability in the component /jmreport/show of jeecg boot v3.0.0 to v3.5.3 allows attackers to execute arbitrary code via a crafted HTTP request.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

A command injection vulnerability exists in the /jmreport/show endpoint of jeecg boot v3.0.0 through v3.5.3. Attackers can send crafted HTTP requests to execute arbitrary OS commands on the target system due to insufficient input validation in the report rendering component.

MitigationUpgrade jeecg boot to version 3.5.4 or later, which contains the patched version. If immediate patching is not possible, disable or restrict access to the /jmreport/show endpoint at the network or application level.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Jeecg BootApplication
Affected:>= 3.0, <= 3.5.3

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Jeecg Boot version
    Check the pom.xml file, application.yml/properties, or the JAR/WAR manifest for the jeecg-boot version number. Common locations: src/main/resources/application.yml or the built artifact's version metadata.
    Affected if The installed version is between 3.0.0 and 3.5.3 inclusive.
  2. Verify jmreport module is present
    Search for jmreport-related JAR files in the lib or WEB-INF/lib directory of the deployed application, or check if jmreport dependency exists in the project's pom.xml.
    Affected if The jmreport module is included in the deployment.
  3. Confirm /jmreport/show endpoint exists
    Review the application's routing configuration or Swagger/OpenAPI documentation. For a running application, send a HEAD request to /jmreport/show or check the deployed WAR/JAR's controller mappings.
    Affected if The /jmreport/show endpoint is registered and accessible.
  4. Check network exposure of the endpoint
    Review firewall rules, security groups, or reverse proxy configuration to determine if the /jmreport/show endpoint is reachable from untrusted networks.
    Affected if The endpoint is exposed to the internet or untrusted internal networks without authentication.

You are affected if you are running Jeecg Boot version 3.0.0 through 3.5.3 with the jmreport module enabled and the /jmreport/show endpoint is accessible to potential attackers.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 3.5.3
Interim mitigation

Upgrade jeecg boot to version 3.5.4 or later, which contains the patched version. If immediate patching is not possible, disable or restrict access to the /jmreport/show endpoint at the network or application level.

Recommended fix Moderate confidence

Latest stable Jeecg Boot release (version > 3.5.3)

  1. 1. Identify current Jeecg Boot version by checking pom.xml or application.properties for the jeecg-boot version property
  2. 2. Download or pull the latest stable Jeecg Boot release from the official repository (github.com/jeecgboot/JeecgBoot)
  3. 3. Review the release notes between current version and latest version for any breaking changes or migration requirements
  4. 4. Update the jeecg-boot version in pom.xml to the latest stable release (version > 3.5.3)
  5. 5. Rebuild the application with mvn clean package -DskipTests
  6. 6. Deploy the updated application to your test environment
  7. 7. Verify the /jmreport/show endpoint no longer accepts malicious command injection payloads
  8. 8. Run regression tests to ensure existing report functionality works correctly
Caveat Review release notes for migration steps; major version jumps may require database schema updates and configuration changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Jeecg Boot Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,720
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,752.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-43028 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-43028 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data