CVE-2023-41544
RCE in Jeecg Boot ≤ 3.5.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HCVSS and EPSS are reproduced from their sources (NVD, FIRST EPSS). EPSS, Forum of Incident Response and Security Teams (FIRST), epss.first.org. Risk Priority is our own derived reading, not an NVD score.
Summary
CVE-2023-41544 is a critical-severity Code Injection (CWE-94) vulnerability in Jeecg Boot. Its CVSS base score is 9.8 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked in the top 14% of CVEs by exploit likelihood; it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2023-41544 is a server-side template injection (SSTI) flaw, tracked under CWE-94, that affects Jeecg-Boot version 3.5.3. The vulnerability resides in the /jmreport/loadTableData endpoint and permits an attacker to supply a crafted HTTP request that is processed by the template engine, resulting in arbitrary code execution on the server.
Unauthenticated remote attackers can exploit the issue over the network by sending a malicious payload in a single request. Successful exploitation grants full control of the application process, allowing arbitrary command execution, data exfiltration, or further lateral movement within the affected environment. The CVSS 3.1 base score of 9.8 reflects the absence of required authentication or user interaction and the complete compromise of confidentiality, integrity, and availability.
The current EPSS score of 0.1762 indicates moderate but non-negligible exploitation interest following public disclosure. Public references consist of technical write-ups that demonstrate proof-of-concept requests against the vulnerable endpoint; no official vendor patch or mitigation guidance is referenced in the supplied sources.
OWASP Top 10 for Web (2025)
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2023-3095
Vulnerability Data
SSTI injection vulnerability in jeecg-boot version 3.5.3, allows remote attackers to execute arbitrary code via crafted HTTP request to the /jmreport/loadTableData component.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
MITRE ATT&CK v20.0
CVEs Like This One
Affected Assets
Mitigating Controls
Control response
—
—
—
V1.3.1
Likely Mitigating Controls
Our mappings. Per-CVE control mapping for this CVE has not run yet; the list below is derived from the weakness types (CWEs) cited in the NVD entry.
Makes persistent code injection into loaded programs impossible when the executable image itself resides on hardware-protected read-only media.
Dynamically generated code can be produced and executed inside the isolated chamber, preventing host compromise from code-injection payloads.
Validates inputs used in dynamic code generation to block injected directives.
Directly prevents execution of attacker-supplied code written into data memory regions.
Mitigating Controls (NIST CSF 2.0)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→CSF cross-walk — links open the control.
PR.PS-06's SDLC practices directly target injection flaws via secure coding and testing (mostly), yet as a single broad outcome it leaves many code-generation specifics unaddressed (partial).
Mitigating Controls (ISO/IEC 27001:2022 Annex A)
Our mappings, derived directly from the weakness types (CWEs) cited in the NVD entry via our CWE→ISO cross-walk — links open the control.
A.8.29's programme of code review, static analysis, dynamic testing and penetration testing is the complete pre-production discovery set for code injection: eval/dynamic-execution sinks are visible to SAST, code review catches them, and penetration testing reaches the externally exploitable instances, with no nameable remainder.
Training technical teams in secure coding practices (per A.6.3's education and training guidance) helps developers avoid constructing code from untrusted input without neutralization, but the effect is a minority one because the clause mandates a general awareness/training practice rather than a specific secure-coding mechanism, and developers remain fallible.
Banning unapproved code samples and unauthenticated web services, combined with secure-coding standards and SAST, prevents the dynamic generation or inclusion of attacker-supplied code.
A.8.30 carries its effect through the secure-development practices its contract requires of the supplier (8.25 to 8.29), so it reduces ordinary software weaknesses like code injection in delivered code the way those practices do, at `partial` -- the effect depends on the supplier's faithful implementation of those practices, which is fallible, and the clause sits at its declared ceiling of `partial` on this verb.
A.8.8's reach is DISCLOSURE — it sees only instances that carry a vendor-published flaw in third-party components. CWE-94 (code injection) does surface as CVEs in some libraries and frameworks, so A.8.8 finds that minority; the bulk of code injection lives in first-party code (eval(), dynamic code generation in the organization's own application), which A.8.8 does not reach — that is the job of SAST/DAST under A.8.29.