dbcve.org
OnlineApplication · Collabora

CVE-2025-66208

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-03
Fix available
A fix is available. Upgrade to 25.04.702 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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 - Built-in CODE Server (richdocumentscode) provides a built-in server with all of the document editing features of Collabora Online. In versions prior to 25.04.702, Collabora Online has a Configuration-Dependent RCE (OS Command Injection) in richdocumentscode proxy. Users of Nextcloud with Collabora Online - Built-in CODE Server app can be vulnerable to attack via proxy.php and an intermediate reverse proxy. This vulnerability is fixed in 25.04.702.

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

OS Command Injection vulnerability in the richdocumentscode proxy component of Collabora Online's built-in CODE server, allowing remote attackers to execute arbitrary commands through proxy.php when used with an intermediate reverse proxy configuration.

MitigationUpdate to Collabora Online - Built-in CODE Server version 25.04.702 or later. Review and properly secure the proxy.php configuration and reverse proxy setup to prevent abuse.

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
OnlineApplication
Affected:< 25.04.702

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 Collabora Online installation
    Locate the Collabora Online application or CODE server installation and determine its package or application version number
    Affected if Version is present but cannot be determined to be 25.04.702 or higher
  2. Determine installed version against affected range
    Compare your installed Collabora Online version to the affected range of versions prior to 25.04.702
    Affected if Installed version is below 25.04.702
  3. Check if richdocumentscode proxy component is in use
    Inspect the deployment for the presence and usage of the richdocumentscode proxy component, typically involving proxy.php in the web server configuration
    Affected if The richdocumentscode proxy component is present and accessible via proxy.php
  4. Verify reverse proxy configuration exists
    Examine the web server or proxy configuration for any intermediate reverse proxy setup handling requests to Collabora Online
    Affected if A reverse proxy configuration forwards traffic to the Collabora Online proxy.php endpoint

You are affected if Collabora Online or built-in CODE server version is below 25.04.702 AND the richdocumentscode proxy component with proxy.php is accessible through a reverse proxy configuration.

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 25.04.702 or later
Fixed in 25.04.702
Vendor patch github.com →
Interim mitigation

Update to Collabora Online - Built-in CODE Server version 25.04.702 or later. Review and properly secure the proxy.php configuration and reverse proxy setup to prevent abuse.

Recommended fix High confidence

25.04.702

  1. 1. Back up your current Collabora Online - Built-in CODE Server (richdocumentscode) installation and configuration
  2. 2. Upgrade the Collabora Online - Built-in CODE Server to version 25.04.702 or later
  3. 3. Restart the Collabora Online services to load the patched code
  4. 4. Verify the upgrade was successful by checking the version number in the admin interface
  5. 5. Test that document editing functionality continues to work correctly after the upgrade

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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