dbcve.org
Cross-site Scripting (XSS)Weakness · CWE-79

CVE-2023-42345

MEDIUM · 6.1 CVSS v3.1 Published 2026-05-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
A Cross Site Scripting vulnerability in Alkacon OpenCms before 16 exists via updateModelGroups.jsp.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

A reflected Cross-Site Scripting (XSS) vulnerability exists in Alkacon OpenCms before version 16, specifically in the updateModelGroups.jsp endpoint. Attackers can inject malicious JavaScript payloads through unsanitized user input processed by this JSP file, potentially executing in victim browsers.

MitigationUpgrade to Alkacon OpenCms version 16 or later to obtain the security patch. If immediate upgrade is not feasible, implement input validation and output encoding on the updateModelGroups.jsp endpoint to sanitize user-supplied data before rendering.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Alkacon OpenCms installation
    Look for the OpenCms directory structure in your web server's deployment folder (commonly under /webapps/ in Tomcat or the equivalent for your application server). The presence of a folder named 'opencms' or 'ALKACON_OPENCMS' indicates an installation.
    Affected if Alkacon OpenCms is present on the server
  2. Determine installed OpenCms version
    Check the version file or manifest. Common locations include: /WEB-INF/org/opencms/version.xml, /WEB-INF/opencms.properties, or a version.txt file in the OpenCms root directory. Compare your version number to the affected range (versions before version 16).
    Affected if The installed version is 15.x or earlier, or the version cannot be determined and is assumed to be pre-16
  3. Locate the vulnerable JSP file
    Search for the updateModelGroups.jsp file in the web application deployment. Common paths include: /WEB-INF/jsp/updateModelGroups.jsp, /jsp/updateModelGroups.jsp, or within a modules subdirectory under the OpenCms web root.
    Affected if The updateModelGroups.jsp file exists in the deployment
  4. Check endpoint accessibility
    Verify the JSP is accessible by attempting to access the URL path where updateModelGroups.jsp is located through your web server. Check for any URL mappings or filters that may restrict access to this endpoint.
    Affected if The endpoint is publicly accessible without authentication or input sanitization checks in place

You are affected if Alkacon OpenCms version 15.x or earlier is installed and the updateModelGroups.jsp file exists and is accessible in your environment.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Alkacon OpenCms version 16 or later to obtain the security patch. If immediate upgrade is not feasible, implement input validation and output encoding on the updateModelGroups.jsp endpoint to sanitize user-supplied data before rendering.

Recommended fix Moderate confidence

Alkacon OpenCms version 16

  1. 1. Identify the current Alkacon OpenCms version in use
  2. 2. Download Alkacon OpenCms version 16 from the official Alkacon website or GitHub repository
  3. 3. Review the upgrade documentation for migrating from your current version to version 16
  4. 4. Perform a full backup of the existing OpenCms installation and database
  5. 5. Test the upgrade in a non-production environment first
  6. 6. Apply the upgrade following the documented migration procedure
  7. 7. Verify that the updateModelGroups.jsp functionality works correctly post-upgrade
  8. 8. Confirm the XSS vulnerability is resolved by testing the updateModelGroups.jsp endpoint with benign input

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42345 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2023-42345 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data