dbcve.org
OpencmsApplication · Alkacon

CVE-2023-6380

MEDIUM · 6.1 CVSS v3.1 Published 2023-12-13
Fix available
A fix is available. Upgrade to 16.0.0 or later.
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
Open redirect vulnerability has been found in the Open CMS product affecting versions 14 and 15 of the 'Mercury' template. An attacker could create a specially crafted URL and send it to a specific user to redirect them to a malicious site and compromise them. Exploitation of this vulnerability is possible due to the fact that there is no proper sanitization of the 'URI' parameter.

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 · high confidence

Open redirect vulnerability in Open CMS Mercury template versions 14 and 15 allows attackers to craft malicious URLs via the unsanitized 'URI' parameter, enabling phishing and credential theft through user redirection to attacker-controlled sites.

MitigationImplement strict allowlist-based validation of the URI parameter and ensure all redirects validate the destination URL against trusted domains before execution.

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

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
OpencmsApplication
Affected:>= 14.0.0, < 16.0.0

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 OpenCms installation version
    Locate the OpenCms WAR file or deployment directory and check the version manifest. Common locations include the manifest file in the WEB-INF folder or the system admin interface under 'Version Information'.
    Affected if Installed version is 14.0.0 or higher but lower than 16.0.0
  2. Confirm Mercury template is deployed
    Check for the presence of the Mercury template module in the OpenCms templates directory. This is typically found under /system/modules/ or within the deployed web application's template folders.
    Affected if Mercury template module exists in the installation
  3. Verify URI parameter handling is accessible
    Test for the open redirect endpoint by observing how the application handles a URI parameter in URL requests to Mercury template pages. This may appear in login, navigation, or redirect-handling code.
    Affected if The application processes and follows redirects based on a URI parameter without validation
  4. Review redirect logic in template code
    Inspect the Mercury template source files for redirect or URI parameter handling logic. Look for code that reads a URI parameter and performs a forward or redirect operation.
    Affected if Redirect logic exists that uses unsanitized URI parameter input
  5. Check for allowlist validation on redirects
    Examine the redirect validation code to determine if destination URLs are validated against a trusted domain allowlist before execution.
    Affected if No allowlist-based validation is implemented for URI parameter redirects

You are affected if running Alkacon OpenCms version 14.0.0 through 15.x with the Mercury template and the application allows redirect via an unsanitized URI parameter without domain allowlist validation.

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
Upgrade available Upgrade to 16.0.0 or later
Fixed in 16.0.0
Interim mitigation

Implement strict allowlist-based validation of the URI parameter and ensure all redirects validate the destination URL against trusted domains before execution.

Recommended fix Moderate confidence

OpenCMS 16.0.0

  1. 1. Backup your current OpenCMS installation and database before proceeding.
  2. 2. Download OpenCMS version 16.0.0 or later from the official OpenCMS repository or distribution channel.
  3. 3. Review the upgrade documentation for migrating from version 14/15 to version 16.
  4. 4. Deploy the new version following the standard OpenCMS upgrade procedure.
  5. 5. Verify that the Mercury template has been updated and the URI parameter is now properly sanitized.
  6. 6. Test that open redirect payloads in the URI parameter are no longer accepted.
  7. 7. Monitor for any issues after deployment.

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

Fix this in Opencms 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 the upgrade done

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-6380 — 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-6380 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