VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

com.jfinal:jfinal: vulnerability history, versions and safety

com.jfinal:jfinal is a package in the Maven ecosystem. Vulert records 36 vulnerabilities for it across 81 releases, from Aug 2021 to Jan 2024. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
36 vulnerabilities recorded C2 H21 M13
i
34 with no fix published

No patched version yet — these are the ones to plan around.

See the unfixed vulnerabilities →
i
0 in the last 12 months

Nothing new recorded in the last year.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all com.jfinal:jfinal vulnerabilities

Vulert verdict on com.jfinal:jfinal 5.3.0 i

Updated on 23 Oct 2026

Careful: 5.3.0 has 34 known vulnerabilities, and 34 have no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 50/100
  • Security Unfixed issues
  • Maintenance Sustainable
  • Popularity Niche
  • Community Quiet

The current release has a vulnerability with no published fix, which caps this score.

What to do: Pin an earlier, unaffected release if you can, and apply the workaround each vulnerability lists until a fix is published. No fix yet: Vulert alerts you the moment one is published. Monitor it with Vulert →

  • Current release 5.3.0 — affected i
  • Vulnerabilities on record 36 over 2 years · 0 in the last year i
  • Latest disclosure 23 Jan 2024 i
  • Highest CVSS 9.8 i
  • With no published fix 34 i
  • Depended on by 6 packages i
  • Stars 3,270 i
  • OpenSSF scorecard 2/10 i
  • Last release 2 months ago i
  • Licence Apache-2.0 i

Version list, release dates, licence and dependants published by Maven Central, refreshed 23 Oct 2026. Licence information is not legal advice.

Concerned about your application's security?

Vulert continues monitoring your dependencies and alerts you when new vulnerabilities are disclosed. No installation and no source-code access required.

01 Versions

Which versions are affected

Every version Vulert tracks for com.jfinal:jfinal, newest first, with the vulnerabilities recorded against each one. A version showing none has no vulnerability in the Vulert database — open it for the full picture on that release.

i
Version Released Vulert vulnerabilities Licence Fix published Details
5.3.0 20 Aug 2026 C2 H20 M12 Apache-2.0 No Details →
5.2.8 16 Jul 2026 C2 H20 M12 Apache-2.0 No Details →
5.2.7 19 Jul 2025 C2 H20 M12 Apache-2.0 No Details →
5.2.6 12 Jun 2025 C2 H20 M12 Apache-2.0 No Details →
5.2.5 29 May 2025 C2 H20 M12 Apache-2.0 No Details →
5.2.4 12 Jan 2025 C2 H20 M12 Apache-2.0 No Details →
5.2.3 16 Sep 2024 C2 H20 M12 Apache-2.0 No Details →
5.2.2 29 Aug 2024 C2 H20 M12 Apache-2.0 No Details →
5.2.1 28 Jul 2024 C2 H20 M12 Apache-2.0 No Details →
5.2.0 26 Jun 2024 C2 H20 M12 Apache-2.0 No Details →
5.1.9 24 May 2024 C2 H20 M12 Apache-2.0 No Details →
5.1.8 14 May 2024 C2 H20 M12 Apache-2.0 No Details →
5.1.7 29 Feb 2024 C2 H20 M12 Apache-2.0 No Details →
5.1.6 14 Jan 2024 C2 H20 M12 Apache-2.0 No Details →
5.1.5 03 Oct 2023 C2 H20 M12 Apache-2.0 No Details →
5.1.4 02 Oct 2023 C2 H20 M12 Apache-2.0 No Details →
5.1.3 24 Sep 2023 C2 H20 M12 Apache-2.0 No Details →
5.1.2 22 Aug 2023 C2 H20 M12 Apache-2.0 No Details →
5.1.1 03 Jun 2023 C2 H20 M12 Apache-2.0 No Details →
5.1.0 06 May 2023 C2 H20 M12 Apache-2.0 No Details →
5.0.9 05 May 2023 C2 H20 M12 Apache-2.0 No Details →
5.0.8 10 Dec 2022 M1 Apache-2.0 No Details →
5.0.7 26 Nov 2022 M1 Apache-2.0 No Details →
5.0.6 01 Nov 2022 M1 Apache-2.0 No Details →
5.0.5 17 Oct 2022 M1 Apache-2.0 No Details →
5.0.4 12 Oct 2022 M1 Apache-2.0 No Details →
5.0.3 18 Sep 2022 M1 Apache-2.0 No Details →
5.0.2 07 Aug 2022 M1 Apache-2.0 No Details →
5.0.1 05 Jun 2022 M1 Apache-2.0 No Details →
5.0.0 03 May 2022 H20 M12 Apache-2.0 No Details →
4.9.23 17 Apr 2022 H20 M12 Apache-2.0 No Details →
4.9.22 05 Apr 2022 H20 M12 Apache-2.0 No Details →
4.9.21 06 Mar 2022 H20 M12 Apache-2.0 No Details →
4.9.20 27 Feb 2022 H20 M12 Apache-2.0 No Details →
4.9.19 20 Feb 2022 H20 M12 Apache-2.0 No Details →
4.9.18 13 Feb 2022 H20 M12 Apache-2.0 No Details →
4.9.17 14 Sep 2021 H20 M12 Apache-2.0 No Details →
4.9.16 08 Aug 2021 H20 M12 Apache-2.0 No Details →
4.9.15 04 Jul 2021 H20 M12 Apache-2.0 No Details →
4.9.14 27 Jun 2021 H20 M12 Apache-2.0 No Details →
4.9.13 22 Jun 2021 H20 M12 Apache-2.0 No Details →
4.9.12 19 Jun 2021 H20 M12 Apache-2.0 No Details →
4.9.11 23 May 2021 H20 M12 Apache-2.0 No Details →
4.9.10 26 Apr 2021 H20 M13 Apache-2.0 No Details →
4.9.09 07 Apr 2021 H20 M13 Apache-2.0 No Details →
4.9.08 03 Mar 2021 C2 H20 M13 Apache-2.0 No Details →
4.9.07 07 Feb 2021 C2 H20 M13 Apache-2.0 No Details →
4.9.06 01 Jan 2021 C2 H20 M13 Apache-2.0 No Details →
4.9.05 07 Dec 2020 C2 H20 M13 Apache-2.0 No Details →
4.9.04 05 Dec 2020 C2 H20 M13 Apache-2.0 No Details →
4.9.03 08 Nov 2020 C2 H20 M13 Apache-2.0 No Details →
4.9.02 03 Oct 2020 C2 H20 M13 Apache-2.0 No Details →
4.9.01 24 Jul 2020 C2 H20 M13 Apache-2.0 No Details →
4.9 25 May 2020 C2 H20 M13 Apache-2.0 No Details →
4.8 09 Dec 2019 C2 H20 M13 Apache-2.0 No Details →
4.7 29 Oct 2019 C2 H20 M13 Apache-2.0 No Details →
4.6 13 Oct 2019 C2 H20 M13 Apache-2.0 No Details →
4.5 01 Sep 2019 C2 H20 M13 Apache-2.0 No Details →
4.4 20 Aug 2019 C2 H21 M13 Apache-2.0 No Details →
4.3 03 Jul 2019 C2 H21 M13 Apache-2.0 No Details →
4.2 02 Jun 2019 C2 H21 M13 Apache-2.0 No Details →
4.1 29 May 2019 C2 H21 M13 Apache-2.0 No Details →
4.0 19 May 2019 C2 H21 M13 Apache-2.0 No Details →
3.8 06 Apr 2019 C2 H21 M13 Apache-2.0 No Details →
3.7 19 Mar 2019 C2 H21 M13 Apache-2.0 No Details →
3.6 30 Jan 2019 C2 H21 M13 Apache-2.0 No Details →
3.5 07 Oct 2018 C2 H21 M13 Apache-2.0 No Details →
3.4 25 Apr 2018 C2 H21 M13 Apache-2.0 No Details →
3.3 21 Nov 2017 C2 H21 M13 Apache-2.0 No Details →
3.2 05 Aug 2017 C2 H21 M13 Apache-2.0 No Details →
3.1 04 May 2017 C2 H21 M13 Apache-2.0 No Details →
3.0 18 Jan 2017 C2 H21 M13 Apache-2.0 No Details →
2.2 18 Jan 2016 C2 H21 M13 Apache-2.0 No Details →
2.1 11 Jan 2016 C2 H21 M13 Apache-2.0 No Details →
2.0 22 Jun 2015 C2 H21 M13 Apache-2.0 No Details →
1.9 09 Nov 2014 C2 H21 M13 Apache-2.0 No Details →
1.8 25 May 2014 C2 H21 M13 Apache-2.0 No Details →
1.6 01 Apr 2014 C2 H21 M13 Apache-2.0 No Details →
1.5 09 Oct 2013 C2 H21 M13 Apache-2.0 No Details →
1.4 08 Sep 2013 C2 H21 M13 Apache-2.0 No Details →
1.4.0 08 Sep 2013 C2 H21 M13 Apache-2.0 No Details →

All 81 versions Vulert tracks for this package. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 3
  • 2023 28
  • 2024 4

Counted by the year Vulert recorded each vulnerability — the same date the table below shows as disclosed. 0 of the 36 were recorded in the last 12 months.

03 Vulnerabilities

Recorded vulnerabilities for com.jfinal:jfinal

The 5 most severe of 36 vulnerabilities recorded for this package

Search all 36 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2021-31635: jFinal Server-Side Template Injection vulnerability 9.8 critical No fix published 26 Jun 2023
Cross-Site Request Forgery in JFinalCMS via /admin/category/update 8.8 high No fix published 05 Dec 2023
CVE-2023-49372: Cross-Site Request Forgery in JFinalCMS 8.8 high No fix published 05 Dec 2023
Cross-Site Request Forgery in JFinalCMS 8.8 high No fix published 05 Dec 2023
CVE-2023-49375: Cross-Site Request Forgery in JFinalCMS via /admin/friend_link/update 8.8 high No fix published 05 Dec 2023

Vulnerability wrong, a fix missing, or a package we should cover? Report it and we will fix the record. Report Vulnerability Provide Feedback

Updated: 23/Oct/2026 · Vulnerabilities in our DB: 524315

Subscribe to Vulert on Telegram
Daily digest of new CVEs, critical and high severity, affected packages and fixes — plus a weekly roundup.
Join the channel →

Questions

About com.jfinal:jfinal

Is com.jfinal:jfinal safe to use?

Vulert records 36 vulnerabilities for com.jfinal:jfinal in Maven: 2 critical, 21 high, 13 medium and 0 low. 34 of them have no published fix yet, so those are the ones to avoid or mitigate.

What is com.jfinal:jfinal's Vulert package health score?

Vulert scores com.jfinal:jfinal 50/100, which reads as usable, but worth attention. The score weighs the vulnerability record (40), maintenance and release cadence (25), adoption from dependents and stars (20) and community signals such as the OpenSSF scorecard and forks (15). The current release has a vulnerability with no published fix, which caps this score.

Is the latest version of com.jfinal:jfinal affected?

Yes. 5.3.0, the version you would install today, has 34 known vulnerabilities, and 34 has no published fix yet. Use an earlier unaffected release, or the workaround each vulnerability lists.

Which version of com.jfinal:jfinal should I use?

5.3.0 is the version Vulert recommends for the affected releases. The version table above lists every release with the vulnerabilities recorded against it, so you can confirm the range you actually run.

How many vulnerabilities does com.jfinal:jfinal have?

36 vulnerabilities are recorded for com.jfinal:jfinal in the Maven ecosystem: 2 critical, 21 high, 13 medium and 0 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new com.jfinal:jfinal vulnerabilities disclosed?

0 vulnerabilities were recorded for com.jfinal:jfinal in the last 12 months, and the oldest entry in this database dates to 13 Aug 2021. Recency matters more than a lifetime total: it shows how actively new issues are being disclosed for the package you are considering.

Which versions of com.jfinal:jfinal are affected?

Each vulnerability on this page lists the affected version range and the fixed version to move to. Open the vulnerability for the version you actually run — fixes are specific to a release line, not to the package as a whole.

How do I monitor com.jfinal:jfinal for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at vulert.com/scanner and Vulert keeps checking the com.jfinal:jfinal version you actually run against new disclosures, then alerts you when one affects it. There is no installation and no source-code access required.