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

CVE-2023-42343

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 10.5.1 exists via cmis-online/type.

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 Cross Site Scripting (XSS) vulnerability exists in Alkacon OpenCms versions prior to 10.5.1. The vulnerability is located in the cmis-online/type parameter, allowing attackers to inject malicious scripts that execute in the context of a victim's browser when accessing the affected functionality.

MitigationUpgrade Alkacon OpenCms to version 10.5.1 or later to remediate this vulnerability. If immediate upgrading is not possible, implement input validation and output encoding on the cmis-online/type endpoint as a temporary mitigation.

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. Confirm Alkacon OpenCms is installed
    Look for OpenCms installation directories (typically under /opt/opencms, /var/www/opencms, or similar web root paths). Check for the presence of OpenCms-specific directories such as /WEB-INF/ and /modules/ within the web application folder.
    Affected if Alkacon OpenCms is not present on the system
  2. Identify the installed OpenCms version
    Locate the version file or manifest. Common locations include: WEB-INF/org/opencms/*, /opencms/system/info/version.txt, or check the admin interface under 'System Administration' > 'System Info'. Compare the found version number against the affected range (versions prior to 10.5.1).
    Affected if The installed version is earlier than 10.5.1 (e.g., 10.5.0, 10.0.x, 9.x, etc.)
  3. Verify the CMIS-online module is enabled
    Check if the CMIS module is deployed. Look for the cmis-online module directory under /modules/ in the OpenCms installation, or check the module configuration file at /WEB-INF/modules/org.opencms.cmismodule.xml if it exists.
    Affected if The cmis-online module directory or configuration file exists and is enabled in the OpenCms module list
  4. Confirm access to the vulnerable cmis-online/type endpoint
    Attempt to access the URL pattern /opencms/opencms/cmis-online/ in the web browser or via curl. The vulnerability lies in the 'type' parameter (e.g., /opencms/opencms/cmis-online/?type=<script>). If the endpoint returns a response rather than a 404, the parameter is accessible.
    Affected if The cmis-online endpoint is accessible and accepts the 'type' parameter without sanitization

A user is affected if Alkacon OpenCms version 10.5.0 or earlier is installed AND the cmis-online module is enabled AND the vulnerable type parameter is accessible.

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 Alkacon OpenCms to version 10.5.1 or later to remediate this vulnerability. If immediate upgrading is not possible, implement input validation and output encoding on the cmis-online/type endpoint as a temporary mitigation.

Recommended fix Moderate confidence

Alkacon OpenCms 10.5.1

  1. 1. Backup your current Alkacon OpenCms installation and database
  2. 2. Download Alkacon OpenCms version 10.5.1 from the official Alkacon website or release repository
  3. 3. Review the upgrade documentation for 10.5.1
  4. 4. Deploy version 10.5.1 following the standard upgrade procedure
  5. 5. Verify the cmis-online/type endpoint is functioning correctly after upgrade
  6. 6. Test that the XSS vulnerability is remediated by attempting to inject script tags via the vulnerable parameter
Caveat Review Alkacon OpenCms 10.5.1 release notes for any breaking changes or database migration requirements before upgrading

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
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,930
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-42343 — 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-42343 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