VulertSecurity VulertSecurity

Vulnerability Database · Maven · Package report

org.apache.wicket:wicket-core: vulnerability history, versions and safety

org.apache.wicket:wicket-core is a package in the Maven ecosystem. Vulert records 8 vulnerabilities for it across 120 releases, from May 2021 to May 2026. Each vulnerability names the versions it affects, the fixed version to move to, and a workaround where no fix has been published.

i
8 vulnerabilities recorded H5 M3
i
1 with no fix published

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

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

Most recent disclosure 06 May 2026.

See the disclosure history →
i
0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.apache.wicket:wicket-core vulnerabilities

Vulert verdict on org.apache.wicket:wicket-core 10.11.0 i

Updated on 23 Oct 2026

Careful: 10.11.0 has 1 known vulnerability, and 1 has no fix yet. Use an earlier safe version, or the workaround listed for each one.

Package health score 60/100
  • Security Minor issues
  • Maintenance Sustainable
  • Popularity Widely used
  • Community Not enough data

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 10.11.0 — affected i
  • Vulnerabilities on record 8 over 4 years · 1 in the last year i
  • Latest disclosure 06 May 2026 i
  • Highest CVSS 8.8 i
  • With no published fix 1 i
  • Depended on by 371 packages i
  • Last release 1 month 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 org.apache.wicket:wicket-core, 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
9.24.0 24 Aug 2026 M1 Apache-2.0 No Details →
8.19.0 24 Aug 2026 M1 Apache-2.0 No Details →
10.11.0 24 Aug 2026 M1 Apache-2.0 No Details →
10.10.0 22 Jul 2026 M1 Apache-2.0 No Details →
10.9.1 16 May 2026 M1 Apache-2.0 No Details →
8.18.0 10 May 2026 M1 Apache-2.0 No Details →
9.23.0 09 May 2026 M1 Apache-2.0 No Details →
10.9.0 30 Apr 2026 M1 Apache-2.0 No Details →
10.8.0 13 Dec 2025 M1 Apache-2.0 No Details →
9.22.0 13 Dec 2025 M1 Apache-2.0 No Details →
10.7.0 26 Sep 2025 M1 Apache-2.0 No Details →
10.6.0 08 Jul 2025 M1 Apache-2.0 No Details →
9.21.0 20 Apr 2025 M1 Apache-2.0 No Details →
10.5.0 20 Apr 2025 M1 Apache-2.0 No Details →
8.17.0 27 Jan 2025 M1 Apache-2.0 No Details →
9.20.0 21 Jan 2025 M1 Apache-2.0 No Details →
10.4.0 20 Jan 2025 M1 Apache-2.0 No Details →
9.19.0 21 Dec 2024 M1 Apache-2.0 No Details →
10.3.0 13 Dec 2024 M1 Apache-2.0 No Details →
10.2.0 19 Sep 2024 M1 Apache-2.0 No Details →
8.16.0 12 Jun 2024 M2 Apache-2.0 No Details →
10.1.0 28 May 2024 M1 Apache-2.0 No Details →
9.18.0 27 May 2024 M1 Apache-2.0 No Details →
9.17.0 13 Mar 2024 M1 Apache-2.0 No Details →
10.0.0 08 Mar 2024 M1 Apache-2.0 No Details →
9.16.0 23 Nov 2023 M1 Apache-2.0 No Details →
10.0.0-M2 12 Oct 2023 M1 Apache-2.0 No Details →
9.15.0 13 Sep 2023 M1 Apache-2.0 No Details →
10.0.0-M1 12 Jun 2023 M1 Apache-2.0 No Details →
9.14.0 24 May 2023 M1 Apache-2.0 No Details →
8.15.0 26 Apr 2023 M2 Apache-2.0 No Details →
9.13.0 14 Apr 2023 M1 Apache-2.0 No Details →
9.12.0 11 Oct 2022 M1 Apache-2.0 No Details →
9.11.0 06 Jul 2022 M1 Apache-2.0 No Details →
9.10.0 01 May 2022 M1 Apache-2.0 No Details →
9.9.1 04 Apr 2022 M1 Apache-2.0 No Details →
9.9.0 27 Mar 2022 M1 Apache-2.0 No Details →
9.8.0 03 Feb 2022 M1 Apache-2.0 No Details →
8.14.0 29 Jan 2022 M2 Apache-2.0 No Details →
9.7.0 27 Nov 2021 M1 Apache-2.0 No Details →
9.6.0 29 Oct 2021 M1 Apache-2.0 No Details →
9.5.0 06 Sep 2021 M1 Apache-2.0 No Details →
8.13.0 07 Jul 2021 M2 Apache-2.0 No Details →
9.4.0 03 Jul 2021 M1 Apache-2.0 No Details →
7.18.0 02 Apr 2021 M1 Apache-2.0 Yes Details →
8.12.0 30 Mar 2021 M2 Apache-2.0 No Details →
9.3.0 25 Mar 2021 M1 Apache-2.0 No Details →
8.11.0 20 Nov 2020 M2 Apache-2.0 No Details →
9.2.0 15 Nov 2020 H1 Apache-2.0 Yes Details →
9.1.0 07 Oct 2020 H1 Apache-2.0 Yes Details →
8.10.0 03 Oct 2020 M2 Apache-2.0 No Details →
7.17.0 16 Jul 2020 M1 Apache-2.0 Yes Details →
8.9.0 11 Jul 2020 M2 Apache-2.0 No Details →
9.0.0 08 Jul 2020 H1 Apache-2.0 Yes Details →
8.8.0 19 Apr 2020 M2 Apache-2.0 No Details →
9.0.0-M5 02 Apr 2020 M1 Apache-2.0 No Details →
9.0.0-M4 05 Jan 2020 M1 Apache-2.0 No Details →
7.16.0 04 Jan 2020 H1 M1 Apache-2.0 Yes Details →
8.7.0 03 Jan 2020 M2 Apache-2.0 No Details →
9.0.0-M3 11 Sep 2019 M1 Apache-2.0 No Details →
8.6.1 09 Sep 2019 M2 Apache-2.0 No Details →
8.6.0 03 Sep 2019 M2 Apache-2.0 No Details →
7.15.0 03 Sep 2019 H1 M1 Apache-2.0 Yes Details →
9.0.0-M2 29 May 2019 M1 Apache-2.0 No Details →
7.14.0 24 May 2019 H1 M1 Apache-2.0 Yes Details →
8.5.0 24 May 2019 M2 Apache-2.0 No Details →
9.0.0-M1 10 Apr 2019 M1 Apache-2.0 No Details →
7.13.0 02 Apr 2019 H1 M1 Apache-2.0 Yes Details →
8.4.0 01 Apr 2019 M2 Apache-2.0 No Details →
7.12.0 02 Feb 2019 H1 M1 Apache-2.0 Yes Details →
8.3.0 26 Jan 2019 M2 Apache-2.0 No Details →
6.30.0 05 Dec 2018 H1 Apache-2.0 Yes Details →
7.11.0 26 Nov 2018 H1 M1 Apache-2.0 Yes Details →
8.2.0 12 Nov 2018 M2 Apache-2.0 No Details →
8.1.0 10 Sep 2018 M2 Apache-2.0 No Details →
8.0.0 16 May 2018 M2 Apache-2.0 No Details →
6.29.0 17 Feb 2018 H1 Apache-2.0 Yes Details →
7.10.0 11 Feb 2018 H1 M1 Apache-2.0 Yes Details →
8.0.0-M9 11 Feb 2018 M2 Apache-2.0 No Details →
8.0.0-M8 21 Oct 2017 M2 Apache-2.0 No Details →
6.28.0 27 Sep 2017 H1 Apache-2.0 Yes Details →
7.9.0 15 Sep 2017 H1 M1 Apache-2.0 Yes Details →
6.27.1 30 Aug 2017 H1 Apache-2.0 Yes Details →
8.0.0-M7 07 Aug 2017 M2 Apache-2.0 No Details →
7.8.0 08 Jul 2017 H1 M1 Apache-2.0 Yes Details →
6.27.0 02 Jul 2017 H1 Apache-2.0 Yes Details →
8.0.0-M6 14 May 2017 M2 Apache-2.0 No Details →
7.7.0 11 May 2017 H1 M1 Apache-2.0 Yes Details →
8.0.0-M5 25 Mar 2017 M2 Apache-2.0 No Details →
8.0.0-M4 03 Feb 2017 M2 Apache-2.0 No Details →
6.26.0 28 Dec 2016 H1 Apache-2.0 Yes Details →
8.0.0-M3 26 Dec 2016 M2 Apache-2.0 No Details →
7.6.0 26 Dec 2016 H1 M1 Apache-2.0 Yes Details →
1.5.17 26 Oct 2016 H1 Apache-2.0 Yes Details →
6.25.0 19 Oct 2016 H1 Apache-2.0 Yes Details →
8.0.0-M2 19 Oct 2016 M2 Apache-2.0 No Details →
7.5.0 19 Oct 2016 H1 M1 Apache-2.0 Yes Details →
1.5.16 20 Jul 2016 H1 Apache-2.0 Yes Details →
7.4.0 17 Jul 2016 H1 M1 Apache-2.0 Yes Details →
6.24.0 17 Jul 2016 H2 Apache-2.0 Yes Details →
8.0.0-M1 03 Jul 2016 M2 — No Details →
6.23.0 25 Apr 2016 H2 — Yes Details →
7.3.0 25 Apr 2016 H1 M1 — Yes Details →
6.22.0 08 Feb 2016 H2 — Yes Details →
1.5.15 05 Feb 2016 H1 — Yes Details →
7.2.0 20 Jan 2016 H1 M1 — Yes Details →
6.21.0 29 Oct 2015 H2 — Yes Details →
7.1.0 19 Oct 2015 H1 M1 — Yes Details →
1.5.14 18 Oct 2015 H1 — Yes Details →
7.0.0 10 Jul 2015 H1 M1 — Yes Details →
7.0.0-M6 16 Jun 2015 H1 — Yes Details →
6.20.0 09 Jun 2015 H2 — Yes Details →
1.5.13 09 Feb 2015 H1 — Yes Details →
6.19.0 26 Jan 2015 H1 — Yes Details →
7.0.0-M5 26 Jan 2015 H1 — Yes Details →
7.0.0-M4 31 Oct 2014 H1 — Yes Details →
6.18.0 31 Oct 2014 H1 — Yes Details →
1.5.12 04 Sep 2014 H2 — Yes Details →
7.0.0-M3 29 Aug 2014 H1 — Yes Details →
6.17.0 29 Aug 2014 H1 — Yes Details →

The newest 120 of 162 versions Vulert tracks. Severity counts are the vulnerabilities recorded against that exact release.

02 Disclosure history

How often vulnerabilities are recorded

  • 2021 1
  • 2022 5
  • 2025 1
  • 2026 1

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

03 Vulnerabilities

Recorded vulnerabilities for org.apache.wicket:wicket-core

The 5 most severe of 8 vulnerabilities recorded for this package

Search all 8 in the database →
Vulnerability Severity Fixed version ↓ Disclosed ↓
CVE-2016-6806: Apache Wicket CSRF Vulnerability in Wicket Core Packages 8.8 high 6.25.0 17 May 2022
CVE-2020-11976: Apache Wicket - Exposure of Sensitive Information 7.5 high 7.17.0 07 May 2021
CVE-2021-23937: DNS-based Denial of Service in Apache Wicket 7.5 high 9.3.0 24 May 2022
CVE-2014-3526: Apache Wicket Sensitive Data Exposure 7.5 high 1.5.12 13 May 2022
CVE-2014-7808: Apache Wicket Insecure Defaults Leading to Predictable Encrypted URLs 7.5 high 1.5.13 13 May 2022

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 org.apache.wicket:wicket-core

Is org.apache.wicket:wicket-core safe to use?

Vulert records 8 vulnerabilities for org.apache.wicket:wicket-core in Maven: 0 critical, 5 high, 3 medium and 0 low. 1 of them has no published fix yet, so that is the one to avoid or mitigate.

What is org.apache.wicket:wicket-core's Vulert package health score?

Vulert scores org.apache.wicket:wicket-core 60/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 org.apache.wicket:wicket-core affected?

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

Which version of org.apache.wicket:wicket-core should I use?

10.11.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 org.apache.wicket:wicket-core have?

8 vulnerabilities are recorded for org.apache.wicket:wicket-core in the Maven ecosystem: 0 critical, 5 high, 3 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 org.apache.wicket:wicket-core vulnerabilities disclosed?

1 vulnerability was recorded for org.apache.wicket:wicket-core in the last 12 months, and the oldest entry in this database dates to 07 May 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 org.apache.wicket:wicket-core 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 org.apache.wicket:wicket-core for upcoming vulnerabilities?

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