CVE-2024-29182
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 · uneditedCollabora Online is a collaborative online office suite based on LibreOffice. A stored cross-site scripting vulnerability was found in Collabora Online. An attacker could create a document with an XSS payload in document text referenced by field which, if hovered over to produce a tooltip, could be executed by the user's browser. Users should upgrade to Collabora Online 23.05.10.1 or higher. Earlier series of Collabora Online, 22.04, 21.11, etc. are unaffected.
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 confidenceCollabora Online contains a stored cross-site scripting vulnerability where an attacker can embed malicious JavaScript in document text that gets referenced by a field. When users hover over the affected field to display a tooltip, the embedded XSS payload executes in the victim's browser context.
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< 23.05.10.1CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Collabora Online installationCheck the product version through the admin interface of the WOPI host (e.g., Nextcloud or ownCloud admin panel), or query the /hosting/capabilities endpoint if accessible, or run 'docker ps' to identify the Collabora container and check its image tagAffected if Running a container or installation with a version tag visible in the output
-
Determine installed version numberFor Docker: run 'docker images' and note the image tag or digest. For native packages: check the package manager (apt list --installed | grep collabora or similar). Compare the version to 23.05.10.1Affected if Installed version is below 23.05.10.1 (e.g., 23.05.9, 23.05.8, etc.)
-
Verify document editing is enabledConfirm that the Collabora Online service is active and users can upload and edit documents through the WOPI host interface. Check that the 'Edit' functionality is available for supported document types (ODT, DOCX, etc.)Affected if Users can create or edit documents through the Collabora Online interface
-
Confirm field insertion feature is accessibleThis vulnerability affects fields with tooltips. In document editing interfaces, fields can be inserted via Insert > Field commands in the toolbar. Check if users have access to document editing functions that allow field insertion and tooltip textAffected if Users have permission to insert and edit fields in documents
You are affected if your Collabora Online version is below 23.05.10.1 and users can edit documents with field tooltip functionality enabled.
Generated from the published advisory. Verify against your own configuration.
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 · scoped23.05.10.1
Upgrade to Collabora Online version 23.05.10.1 or later. Organizations on earlier branches (22.04, 21.11) are unaffected and do not require action.
Collabora Online 23.05.10.1 or higher
- 1. Identify the currently installed Collabora Online version
- 2. Download or obtain Collabora Online version 23.05.10.1 or later from the official source
- 3. Follow the standard Collabora Online upgrade procedure for your deployment (e.g., Docker, package manager, or system-specific upgrade)
- 4. Verify the upgrade was successful by checking the installed version
- 5. Test that documents with field tooltips render correctly and no XSS payloads execute
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2024-29182 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2024-29182 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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