dbcve.org
Open Xchange AppsuiteApplication · Open Xchange

CVE-2023-41703

MEDIUM · 6.1 CVSS v3.1 Published 2024-02-12
Fix available
A fix is available. Upgrade to 7.10.6 / 8.20 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
User ID references at mentions in document comments were not correctly sanitized. Script code could be injected to a users session when working with a malicious document. Please deploy the provided updates and patch releases. User-defined content like comments and mentions are now filtered to avoid potentially malicious content. 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 · high confidence

This is a stored Cross-Site Scripting (XSS) vulnerability in document comment functionality where user ID references in mentions were not properly sanitized, allowing script code injection that executes in other users' sessions when viewing malicious documents.

MitigationDeploy vendor-provided security updates and patch releases; ensure content filtering is enabled for user-defined content like comments and mentions.

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
Open Xchange AppsuiteApplication
Affected:< 7.10.6> 7.10.6, < 8.20= 7.10.6

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. Verify Open Xchange Appsuite installation
    Identify if the Open Xchange Appsuite platform is deployed in your environment. Check for OX-specific processes, services, or web interfaces typically accessible on ports 8009 or 443.
    Affected if Open Xchange Appsuite is installed and running.
  2. Determine installed Appsuite version
    Locate the version information for your OX Appsuite installation. This is typically available in the admin interface, package manager, or configuration files. Compare your installed version against the affected ranges: versions < 7.10.6, = 7.10.6, and >= 7.10.7 but < 8.20 are vulnerable.
    Affected if Your installed version is 7.10.6, or is lower than 7.10.6, or falls between 7.10.7 and 7.x (including 7.10.7 through 7.x) up to but not including 8.20.
  3. Confirm document comment feature is accessible
    Determine whether users have access to document collaboration features that allow commenting on documents and using @mentions to reference other users.
    Affected if Document commenting and mention functionality is enabled for users in your deployment.
  4. Inspect for existing malicious comments
    Review recent documents and their associated comments for suspicious content, particularly mentions containing script tags or JavaScript event handlers in the user reference fields.
    Affected if Documents contain comments with unsanitized user mentions that could contain injected script code.

You are affected if Open Xchange Appsuite is running and your installed version is below 8.20 while the document comment and mention features are enabled for 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 7.10.6 / 8.20 or later
Fixed in 7.10.68.20
Interim mitigation

Deploy vendor-provided security updates and patch releases; ensure content filtering is enabled for user-defined content like comments and mentions.

Recommended fix High confidence

Open Xchange Appsuite version 8.20 or later (or the latest 7.10.6+ patch if remaining on 7.10.x branch)

  1. Review the Open Xchange Appsuite release notes for version 8.20 and any intermediate patch releases
  2. Plan maintenance window for the upgrade procedure
  3. Backup current installation and database
  4. Upgrade Open Xchange Appsuite to version 8.20 or later
  5. Verify that document comments and mentions functionality works correctly after upgrade
  6. Test that XSS filtering is applied to user-generated content in comments and mentions
Caveat Review release notes for version 8.20 for any breaking changes or deprecated features compared to your current version

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

Fix this in Open Xchange Appsuite Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA6.0 h
30.0 hours of engineering $5,240
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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