SQL Injection in jeecg-boot /jeecg-boot/jmreport/show id parameter
jeecg-boot versions 3.5.0 and 3.5.1 are vulnerable to a SQL injection in the /jeecg-boot/jmreport/show interface via the id parameter. Unsanitized user input in this parameter is directly incorporated into SQL queries, allowing attackers to manipulate the query logic.
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an attacker to execute arbitrary SQL commands in the context of the application's database. This can lead to data exfiltration, modification, or deletion, and potentially full compromise of the underlying database server.
If you can’t patch tonight, do this now.
As an interim measure, restrict access to the vulnerable endpoint, implement web application firewall (WAF) rules to detect and block SQL injection attempts, and validate and sanitize all user input to the /jeecg-boot/jmreport/show endpoint.
Patch, then assume compromise.
Upgrade jeecg-boot to a version where this vulnerability is patched. Ensure that all user-supplied input is properly sanitized and parameterized in SQL queries.
No public exploits tracked yet. Mallory keeps watching.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
1 sources tracked across advisories and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.