dbcve.org
Collabora OnlineApplication · Collaboraoffice

CVE-2023-34088

MEDIUM · 5.4 CVSS v3.1 Published 2023-05-31
Fix available
A fix is available. Upgrade to 6.4.27 / 21.11.9.1 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
Collabora Online is a collaborative online office suite. A stored cross-site scripting (XSS) vulnerability was found in Collabora Online prior to versions 22.05.13, 21.11.9.1, and 6.4.27. An attacker could create a document with an XSS payload as a document name. Later, if an administrator opened the admin console and navigated to the history page, the document name was injected as unescaped HTML and executed as a script inside the context of the admin console. The administrator JSON web token (JWT) used for the websocket connection could be leaked through this flaw. Users should upgrade to Collabora Online 22.05.13 or higher; Collabora Online 21.11.9.1 or higher; Collabora Online 6.4.27 or higher to receive a patch.

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

A stored cross-site scripting (XSS) vulnerability in Collabora Online allows attackers to embed malicious JavaScript in document names. When an administrator accesses the admin console history page, the unsanitized document name is rendered as unescaped HTML, causing the injected script to execute within the admin console's context and exfiltrate the administrator's JWT token.

MitigationUpgrade to Collabora Online version 22.05.13, 21.11.9.1, 6.4.27 or later to receive the patch that properly escapes document names in the admin console.

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
Collabora OnlineApplication
Affected:< 6.4.27>= 21.0, < 21.11.9.1>= 22.0, < 22.05.13

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. Determine Collabora Online version
    Locate the installed Collabora Online version number through the product's package manager, about page, or admin interface
    Affected if The installed version is less than 6.4.27, OR between 21.0.0 and 21.11.9.0 inclusive, OR between 22.0.0 and 22.05.12 inclusive
  2. Identify admin console access
    Determine whether the Collabora Online admin console is deployed and accessible in your environment
    Affected if The admin console is accessible and the vulnerability requires an administrator to view the history page for the XSS to trigger
  3. Locate admin console history feature
    Access the admin console and navigate to the history page or document history section where document names are displayed
    Affected if Document names from user uploads or imports appear in the history view without proper HTML escaping
  4. Check for document name handling
    Inspect how document names are stored and rendered in the admin console interface - look for the history or activity logs that display uploaded document filenames
    Affected if The system displays unsanitized document names in the admin console history, allowing HTML/script content to be rendered unescaped

You are affected if your Collabora Online version falls within the vulnerable ranges AND the admin console history page is accessible, as this is where the stored XSS in document names gets triggered.

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 6.4.27 / 21.11.9.1 / 22.05.13 or later
Fixed in 6.4.2721.11.9.122.05.13
Interim mitigation

Upgrade to Collabora Online version 22.05.13, 21.11.9.1, 6.4.27 or later to receive the patch that properly escapes document names in the admin console.

Recommended fix High confidence

Upgrade to Collabora Online 22.05.13 (or 21.11.9.1 if on 21.x branch, or 6.4.27 if on 6.x branch)

  1. Identify your current Collabora Online version using your package manager or Docker image tag
  2. Determine which upgrade path applies: if you are on version 21.x, upgrade to 21.11.9.1 or later; if on version 22.x, upgrade to 22.05.13 or later; if on version 6.x, upgrade to 6.4.27 or later
  3. If using Docker, stop the current container: 'docker stop collabora' or equivalent
  4. Pull the new fixed image: 'docker pull collabora/code:<new-version>' where <new-version> is 22.05.13, 21.11.9.1, or 6.4.27 as applicable
  5. Remove the old container: 'docker rm collabora'
  6. Start a new container with the fixed image using your original configuration parameters
  7. Verify the new version is running: check the admin console or use 'docker exec <container> version'
  8. Clear any browser cache and verify the admin console history page now properly escapes document names

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

Fix this in Collabora Online Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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