dbcve.org
Ox GuardApplication · Open Xchange

CVE-2023-26456

MEDIUM · 5.4 CVSS v3.1 Published 2023-11-02
Fix available
A fix is available. Upgrade to 2.10.7 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
Users were able to set an arbitrary "product name" for OX Guard. The chosen value was not sufficiently sanitized before processing it at the user interface, allowing for indirect cross-site scripting attacks. Accounts that were temporarily taken over could be configured to trigger persistent code execution, allowing an attacker to build a foothold. Sanitization is in place for product names now. No publicly available exploits are known.

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

This is a stored cross-site scripting (XSS) vulnerability in OX Guard where users could set an arbitrary product name that was not properly sanitized before rendering in the user interface. The unsanitized input allowed indirect XSS attacks, enabling attackers who temporarily took over accounts to configure persistent code execution and establish a foothold.

MitigationThe description indicates sanitization is now in place for product names. Organizations should verify they have deployed the patched version containing the fix.

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
Ox GuardApplication
Affected:< 2.10.7= 2.10.7

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
Low
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/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 OX Guard version
    Check the installed OX Guard package version using your system package manager (dpkg -l | grep guard or rpm -qa | grep guard) or access the OX Guard admin interface and look for version information in the system settings or about page.
    Affected if The installed version is 2.10.7 or lower (any version < 2.10.7 or exactly 2.10.7)
  2. Locate product name setting
    Access the OX Guard administrative interface and navigate to the product branding or settings section where the product name is configured. This may also be stored in OX Guard configuration files depending on your deployment.
    Affected if You can access and view the product name configuration setting in the OX Guard admin panel or configuration files
  3. Inspect product name for unsanitized input
    View the current product name value and examine the rendered HTML in the browser developer tools or view page source. Check if special characters like <, >, ", or ' are being rendered as plain text or executed as HTML/JavaScript.
    Affected if The product name contains raw HTML or JavaScript (such as script tags, event handlers like onload, onerror, or javascript: URIs) that executes when the page renders

You are affected if OX Guard version is 2.10.7 or lower AND the product name field contains malicious script that executes in the browser when viewed by other users.

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 2.10.7 or later
Fixed in 2.10.7
Interim mitigation

The description indicates sanitization is now in place for product names. Organizations should verify they have deployed the patched version containing the fix.

Recommended fix Moderate confidence

Ox Guard 2.10.8 or later

  1. 1. Identify the current Ox Guard version installed in your environment
  2. 2. Download the latest Ox Guard release from the official Open-Xchange software repository (software.open-xchange.com)
  3. 3. Review the release notes for version 2.10.8 or later to confirm the XSS fix is included
  4. 4. Plan maintenance window - schedule during low-usage period
  5. 5. Backup current Ox Guard configuration and data
  6. 6. Upgrade Ox Guard to version 2.10.8 or later
  7. 7. Verify the upgrade was successful and the product name field now properly sanitizes input
  8. 8. Test that the product name functionality works correctly with special characters
Caveat Minimal risk - this is a security patch release; review release notes for any minor behavior changes

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

Fix this in Ox Guard Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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