dbcve.org
Document ServerApplication · Onlyoffice

CVE-2025-68936

MEDIUM · 6.1 CVSS v3.1 Published 2025-12-25
Fix available
A fix is available. Upgrade to 9.2.1 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
ONLYOFFICE Docs before 9.2.1 allows XSS via the Color theme name. This is related to DocumentServer.

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

ONLYOFFICE Docs before 9.2.1 contains a stored Cross-Site Scripting (XSS) vulnerability in the Color theme name parameter within the DocumentServer component. An attacker could inject malicious JavaScript code into the theme name field which would execute in the browsers of other users viewing the themed documents or interface.

MitigationUpgrade ONLYOFFICE Docs to version 9.2.1 or later. Until upgrade is possible, implement input validation and output encoding on the color theme name parameter.

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
Document ServerApplication
Affected:< 9.2.1

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. Check installed ONLYOFFICE DocumentServer version
    Locate the installed version by querying the DocumentServer status command, checking the About section in the web interface, or reviewing version files in the installation directory
    Affected if The version number found is lower than 9.2.1 (for example, 9.2.0, 9.1.x, or earlier)
  2. Confirm DocumentServer component is running
    Verify that the DocumentServer service is active and accessible, typically on port 8000 or 443, or check the running processes for DocumentServer
    Affected if DocumentServer is actively running and accepting connections
  3. Determine if theme customization is accessible
    Check whether the theme settings or color theme configuration feature is available in the DocumentServer interface or API endpoints used for document editing
    Affected if Users can create, modify, or view custom color themes within the document editor

You are affected if your installed ONLYOFFICE DocumentServer version is below 9.2.1 and the DocumentServer with theme customization features is exposed to 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 9.2.1 or later
Fixed in 9.2.1
Interim mitigation

Upgrade ONLYOFFICE Docs to version 9.2.1 or later. Until upgrade is possible, implement input validation and output encoding on the color theme name parameter.

Recommended fix High confidence

ONLYOFFICE Document Server 9.2.1

  1. 1. Back up your current ONLYOFFICE Document Server installation and database before proceeding with any upgrade.
  2. 2. Identify your current installation method (Docker, Linux packages, or Windows installer).
  3. 3. For Docker installations: Run 'docker pull onlyoffice/documentserver:latest' or specifically 'docker pull onlyoffice/documentserver:9.2.1' to pull the fixed version.
  4. 4. Stop and remove the existing container, then recreate it with the new image using your existing configuration.
  5. 5. For Linux packages: Update your package repository and run 'apt-get update && apt-get onlyoffice-documentserver' (or equivalent for your distro) to upgrade to version 9.2.1.
  6. 6. For Windows: Download the ONLYOFFICE Document Server 9.2.1 installer from the official onlyoffice.com website and run the upgrade.
  7. 7. After upgrade, verify the XSS vulnerability is resolved by testing that Color theme names are properly sanitized and no scripts can be injected.
  8. 8. Verify all Document Server services are running correctly and functionality works as expected.
Caveat Review the ONLYOFFICE 9.2.1 release notes for any feature changes or migration requirements before upgrading.

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

Fix this in Document Server Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
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,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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