Is org.opencms:opencms-core safe to use?

Vulert records 31 vulnerabilities for org.opencms:opencms-core in Maven: 0 critical, 3 high, 17 medium and 11 low. 4 of them have no published fix yet, so those are the ones to avoid or mitigate.

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

Vulert scores org.opencms:opencms-core 57/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.opencms:opencms-core affected?

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

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

22.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.opencms:opencms-core have?

31 vulnerabilities are recorded for org.opencms:opencms-core in the Maven ecosystem: 0 critical, 3 high, 17 medium and 11 low. The ledger on this page lists the same counts next to the date of the most recent disclosure.

How often are new org.opencms:opencms-core vulnerabilities disclosed?

4 vulnerabilities were recorded for org.opencms:opencms-core in the last 12 months, and the oldest entry in this database dates to 12 Nov 2019. 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.opencms:opencms-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.opencms:opencms-core for upcoming vulnerabilities?

Upload the manifest or SBOM for your application at https://vulert.com/scanner and Vulert keeps checking the org.opencms:opencms-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.

Vulnerability Database · Maven · Package report

org.opencms:opencms-core: vulnerability history, versions and safety

org.opencms:opencms-core is a package in the Maven ecosystem. Vulert records 31 vulnerabilities for it across 36 releases, from Nov 2019 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.

31 vulnerabilities recorded H3 M17 L11

4 with no fix published

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

See the unfixed vulnerabilities →

4 in the last 12 months

Most recent disclosure 08 May 2026.

See the disclosure history →

0 malicious-package vulnerabilities

No published version shipped hostile code.

See all org.opencms:opencms-core vulnerabilities

Vulert verdict on org.opencms:opencms-core 22.0 i

Updated on 22 Oct 2026

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

Package health score 57/100

Security Some issues to review
Maintenance Sustainable
Popularity Little adoption
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 22.0 — affected i
Vulnerabilities on record 31 over 6 years · 4 in the last year i
Latest disclosure 08 May 2026 i
Highest CVSS 7.8 i
With no published fix 4 i
Last release this month i
Licence non-standard i

Version list, release dates, licence and dependants published by Maven Central, refreshed 22 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.

Scan your app free →

01 Versions

Which versions are affected

Every version Vulert tracks for org.opencms:opencms-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.

Version	Released	Vulert vulnerabilities	Licence	Fix published	Details
22.0	02 Oct 2026	M3 L1	non-standard	No	Details →
21.0	13 Apr 2026	M3 L1	non-standard	No	Details →
20.0	13 Oct 2025	M3 L1	non-standard	No	Details →
19.0	31 Mar 2025	M3 L1	non-standard	No	Details →
18.0	07 Oct 2024	M3 L1	non-standard	No	Details →
17.0	08 Apr 2024	M2 L1	non-standard	No	Details →
16.0	29 Sep 2023	M3 L1	non-standard	No	Details →
15.0	24 Apr 2023	H1 M6 L1	non-standard	No	Details →
14.0	10 Oct 2022	H1 M6 L1	non-standard	No	Details →
13.0	12 Apr 2022	H1 M5 L1	non-standard	No	Details →
12.0	12 Oct 2021	H1 M5 L1	non-standard	No	Details →
11.0.2	14 Aug 2020	H1 M6 L1	non-standard	No	Details →
11.0.1	05 Sep 2019	H1 M6 L1	non-standard	No	Details →
11.0.0	22 May 2019	H1 M11 L1	non-standard	No	Details →
10.5.4	17 May 2018	H2 M10 L2	non-standard	No	Details →
10.5.3	18 Oct 2017	H2 M10 L2	non-standard	No	Details →
10.5.2	12 Jul 2017	H2 M10 L2	non-standard	No	Details →
10.5.1	15 Feb 2017	H2 M10 L2	non-standard	No	Details →
10.5.0	02 Dec 2016	H3 M10 L2	non-standard	No	Details →
10.0.1	15 Jun 2016	H3 M10 L2	non-standard	No	Details →
10.0.0	30 Mar 2016	H3 M10 L2	non-standard	No	Details →
9.5.3	12 Jan 2016	H3 M10 L2	non-standard	No	Details →
9.5.2	23 Jun 2015	H3 M10 L2	non-standard	No	Details →
9.5.1	02 Mar 2015	H3 M10 L3	non-standard	No	Details →
9.5.0	05 Nov 2014	H3 M10 L3	non-standard	No	Details →
9.0.1	07 Feb 2014	H3 M10 L3	non-standard	No	Details →
9.0.0	15 Nov 2013	H3 M10 L3	non-standard	No	Details →
8.5.2	21 Jul 2013	H3 M10 L3	LGPL-2.1	No	Details →
8.5.1	10 Feb 2013	H3 M10 L4	LGPL-2.1	No	Details →
8.5.0	18 Nov 2012	H3 M10 L4	LGPL-2.1	No	Details →
8.0.4	14 Apr 2012	H3 M10 L4	LGPL-2.1	No	Details →
8.0.3.1	08 Jan 2012	H3 M10 L4	LGPL-2.1	No	Details →
8.0.2	07 Jan 2012	H3 M10 L4	LGPL-2.1	No	Details →
8.0.1	05 Jan 2012	H3 M10 L4	LGPL-2.1	No	Details →
8.0.3-rev	07 Dec 2011	H3 M10 L4	LGPL-2.1	No	Details →
8.0.3	02 Dec 2011	H3 M10 L4	LGPL-2.1	No	Details →

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

02 Disclosure history

How often vulnerabilities are recorded

2019 4
2021 1
2022 15
2023 3
2024 1
2025 3
2026 4

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

Other ways into the data

03 Vulnerabilities

Recorded vulnerabilities for org.opencms:opencms-core

Vulnerability	Severity	Fixed version ↓	Disclosed ↓
CSV Injection Vulnerability in Alkacon OpenCMS (org.opencms:opencms-core) - High Risk	7.8 high	11.0.0	24 May 2022
CVE-2023-42346: Alkacon OpenCms XXE Vulnerability in org.opencms:opencms-core	7.5 high	16.0	08 May 2026
CVE-2023-42344: Alkacon OpenCms Remote Information Disclosure via XXE Attack	7.3 high	10.5.1	08 May 2026
CVE-2021-3312: XML External Entity Reference in org.opencms:opencms-core	6.5 medium	12.0.0	12 Oct 2021
OpenCMS Cross-Site Scripting Vulnerability in org.opencms:opencms-core	6.4 medium	17.0	30 May 2024

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

Updated: 22/Oct/2026 · Vulnerabilities in our DB: 524173