CVE-2024-53477: jfinal_cms · n/a
Affects jfinal_cmsSource CVE Database V5
Not known to be exploited · CVSS 9.8 Critical.
Data as of 26 Oct 2026, 06:26 UTC
- EPSS
- 0.8% chance of exploitation in 30 days – higher than 58% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 2 Dec 2024
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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-26.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubjflyfox/jfinal_cmspkg:github/jflyfox/jfinal_cmsOther threats | Affected
| Fixed in– |
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
Until an official patch is released, organizations should implement the following mitigations: 1) Restrict network access to the JFinal CMS server, limiting exposure to trusted IP addresses only. 2) Employ web application firewalls (WAFs) with custom rules to detect and block suspicious deserialization payloads or unusual API requests targeting ApiForm.java endpoints. 3) Conduct thorough input validation and sanitization on all user-supplied data where possible, especially in deserialization routines. 4) Monitor logs for anomalous command execution attempts or unexpected API calls. 5) Isolate the CMS environment from critical internal networks to contain potential breaches. 6) Prepare for rapid patch deployment by tracking vendor advisories and testing updates in controlled environments. 7) Consider disabling or restricting features related to deserialization if configurable. These targeted steps go beyond generic advice by focusing on network segmentation, proactive detection, and containment strategies specific to deserialization vulnerabilities in JFinal CMS.
Description
JFinal CMS 5.1.0 is vulnerable to Command Execution via unauthorized execution of deserialization in the file ApiForm.java