Skip to main content
ExploitedNot in CISA KEV yetFix available

CVE-2023-4450

Exploitation confirmed. First attested on 2024-08-06 by GCVE · kevintel, GCVE · shadowserver.

  • Published2023-08-21
  • Fixed in1.6.1
  • WeaknessCWE-74

Am I affected?

With a domain, we read the version its public headers and pages expose. A distribution build can carry the fix under an older number.

Description

A vulnerability was found in jeecgboot JimuReport up to 1.6.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Template Handler. The manipulation leads to injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.6.1 is able to address this issue. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-237571.

Timeline

dates in UTC
  1. 2023-08-2103:15CVE publishedNVD
  2. 2024-08-0602:35Listed as exploited by GCVEGCVE
  3. 2024-08-0602:35Exploitation first reportedGCVE

Observed activity

isMalicious corpus · updated 2026-11-03 15:37 UTC
Indicators tagged with this CVE, per day0 indicators over 7 days
Block these indicators
  • Firewall list (EDL, text): https://api.ismalicious.com/edl/cve/CVE-2023-4450?format=txt
  • CSV export: https://api.ismalicious.com/edl/cve/CVE-2023-4450?format=csv
  • TAXII collection of exploited CVEs
  • The EDL and CSV take an API key on the Pro plan.

Versions per branch

NVD
Jeecg jimureport
BranchAffectedFixed in
1.6< 1.6.11.6.1

as publishedRanges as NVD and OSV publish them; a distribution’s build can be fixed under an older number.

Products declared by the CNA1 product

As VulDB, the CNA that assigned this CVE, declared them in the CVE record; versions as written.

  • jeecgboot JimuReport
    Affected
    • = 1.0no fix stated
    • = 1.1no fix stated
    • = 1.2no fix stated
    • = 1.3no fix stated
    • = 1.4no fix stated
    • = 1.5no fix stated
    • = 1.6no fix stated

Source: the CNA record (CVE Program), © The MITRE Corporation,CVE Terms of UseCVE recordupdated 2024-02-13

Fix

  1. Update Jeecg jimureport to 1.6.1

Detection

read 2026-11-02 22:42 UTC
Nuclei template
available
ProjectDiscovery
Exploit-DB
no entry
Exploit-DB
Proof-of-concept repositories
1 repository, unverifiedilikeoyt/CVE-2023-4450-Attack
PoC-in-GitHub
Metasploit modules
none listed
Metasploit Framework

Sources

Identifiers

Technical details

CVSS v3 Vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Published
2023-08-21
Last Modified
2026-06-17
NVD status
Modified
GitHub Advisory
GHSA-j8h5-8rrr-m6j9

Frequently asked questions

What is CVE-2023-4450?

A vulnerability was found in jeecgboot JimuReport up to 1.6.0. It has been declared as critical. Affected by this vulnerability is an unknown functionality of the component Template Handler. The manipulation leads to injection. The attack can be launched remotely. The exploit has been disclosed to the public and may be used. Upgrading to version 1.6.1 is able to address this issue. It is recommended to upgrade the affected component. The associated identifier of this vulnerability is VDB-237571.

Is CVE-2023-4450 actively exploited?

Active exploitation of CVE-2023-4450 has not been confirmed. Its EPSS score was 11.6% on 2026-11-03, the estimated probability of exploitation in the next 30 days.

What is the CVSS score for CVE-2023-4450?

CVE-2023-4450 has a CVSS v3 base score of 9.8 (CRITICAL severity), with vector string CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H.

Running jeecgboot JimuReport? Hear about its next vulnerability

Surveillance reads the versions in your stack — a domain, a lockfile or a list — checks each CVE against the ranges its sources publish, and alerts you when one you run is exploited or enters CISA KEV. A version it cannot read stays « version not verified ».

Get alerts for this productCISA KEV additions, October 2026Search CVEs

No credit card required · No monthly cap on website lookups · 250 API requests/month

Go further

Related vulnerabilities

Same product first, then the same vendor advisory and the same publication week.

Back to CVE Database

Sources for this record