org.opencms:opencms-core vulnerabilities
OpenCms is an enterprise-ready, easy to use website content management system based on Java and XML technology. Offering a complete set of features, OpenCms helps content managers worldwide to create and maintain beautiful websites fast and efficiently.
- Registry
- Maven
- Latest
- 22.0
- License
- GNU Lesser General Public License
31 known advisories
The latest version, 22.0, is not affected by any of them. Projects on older versions may be.
mvn versions:use-dep-version -Dincludes=org.opencms:opencms-core -DdepVersion=22.0 -DforceVersion=trueIs your project on an affected org.opencms:opencms-core?
Look after several Java apps? Indie watches up to 15 repos, private ones too, for $5 a month. See Indie
Security advisories for org.opencms:opencms-core
Alkacon OpenCms is vulnerable to XXE when the <!DOCTYPE> refers to an external host
- Affected
- <16.0
- Fixed in
- 16.0
Alkacon OpenCms allows remote unauthenticated attackers to obtain sensitive information
- Affected
- <10.5.1
- Fixed in
- 10.5.1
Alkacon OpenCms is vulnerable to XSS via updateModelGroups.jsp
- Affected
- <16.0
- Fixed in
- 16.0
Alkacon OpenCms is vulnerable to XSS via cmis-online/type
- Affected
- <16.0
- Fixed in
- 16.0
OpenCMS Cross-Site Scripting vulnerability
- Affected
- <=17.0
- Fixed in
- No fix released
OpenCMS cross-site scripting (XSS) vulnerability
- Affected
- <=17.0
- Fixed in
- No fix released
Alkacon OpenCMS stored cross-site scripting (XSS) vulnerability
- Affected
- <=17.0
- Fixed in
- No fix released
OpenCMS Cross-Site Scripting vulnerability
- Affected
- >=16.0 <17.0
- Fixed in
- 17.0
Alkacon OpenCMS XSS via Mercury template
- Affected
- >=14.0.0 <16.0.0
- Fixed in
- 16.0.0
Alkacon OpenCMS arbitrary file upload vulnerability
- Affected
- <=15.0
- Fixed in
- No fix released
alkacon-OpenCMS vulnerable to stored Cross-site Scripting
- Affected
- <11.0.1
- Fixed in
- 11.0.1
Alkacon OpenCMS XSS via New User module
- Affected
- <11.0.0
- Fixed in
- 11.0.0
Alkacon OpenCMS CSV Injection via New User module
- Affected
- <11.0.0
- Fixed in
- 11.0.0
Alkacon OpenCMS XSS via title and requestedResource parameters
- Affected
- <8.5.2
- Fixed in
- 8.5.2
Alkacon OpenCMS XSS via homelink, workplaceresource, mode and query parameters
- Affected
- <9.5.2
- Fixed in
- 9.5.2
Alkacon OpenCMS XSS via searchfilter parameter in system/workplace/admin/workplace/sessions.jsp
- Affected
- <7.0.4
- Fixed in
- 7.0.4
Alkacon OpenCMS XSS via searchfilter or listSearchFilter parameter
- Affected
- <7.0.4
- Fixed in
- 7.0.4
Alkacon OpenCMS Absolute Path Traversal via pathname in filePath.0 parameter
- Affected
- >=7.0.3 <7.0.5
- Fixed in
- 7.0.5
Alkacon Open CMS XSS via Logfile Viewer Settings function
- Affected
- >=7.0.3 <7.0.5
- Fixed in
- 7.0.5
Alkacon OpenCMS XSS via file tree navigation in system/workplace/views/explorer/tree_files.jsp
- Affected
- <7.0.4
- Fixed in
- 7.0.4
Alkacon OpenCms Exposes JSP Source Code
- Affected
- <6.2.2
- Fixed in
- 6.2.2
Alkacon OpenCMS Improper Access Control via system/workplace/views/admin/admin-main.jsp
- Affected
- <6.2.2
- Fixed in
- 6.2.2
Alkacon OpenCMS Absolute Path Traversal via pathname in filePath parameter
- Affected
- <6.2.2
- Fixed in
- 6.2.2
Alkacon OpenCms XSS via unsanitized message body
- Affected
- <6.2.2
- Fixed in
- 6.2.2
Alkacon OpenCms XSS via query parameter in a search action
- Affected
- >=6.0.0 <6.0.4
- Fixed in
- 6.0.4
Alkacon OpenCms XSS via username during login
- Affected
- <6.0.3
- Fixed in
- 6.0.3
XML External Entity Reference in org.opencms:opencms-core
- Affected
- >=11.0.0 <12.0.0
- Fixed in
- 12.0.0
XSS issues in the management interface
- Affected
- <11.0.1
- Fixed in
- 11.0.1
XSS in login form
- Affected
- <11.0.1
- Fixed in
- 11.0.1
Local file inclusion allows unauthorized access to internal resources in Alkacon OpenCms
- Affected
- <11.0.1
- Fixed in
- 11.0.1
XSS in search engine
- Affected
- <11.0.1
- Fixed in
- 11.0.1
Is your org.opencms:opencms-core version vulnerable?
Which of your client projects still run an old org.opencms:opencms-core?
NPMscan reads the pom.xml, build.gradle and gradle.lockfile in every GitHub repo you pick and checks each installed version against these advisories, including the packages your packages pull in. Each finding comes with the command that fixes it.
Other Maven packages
Advisory data from OSV.dev (opens OSV.dev in a new tab), refreshed daily. Package details from the Maven registry.