CVE-2020-11537
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 · uneditedA SQL Injection issue was discovered in ONLYOFFICE Document Server 5.5.0. An attacker can execute arbitrary SQL queries via injection to DocID parameter of Websocket API.
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 confidenceSQL injection vulnerability in ONLYOFFICE Document Server 5.5.0 allows unauthenticated attackers to execute arbitrary SQL queries via the DocID parameter in the Websocket API. The lack of input sanitization or parameterized queries in the Websocket handler enables attackers to manipulate SQL statements.
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= 5.5.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed ONLYOFFICE Document Server versionRun the command: sudo documentserver --version or check the About section in the Document Server web interface. Alternatively, inspect the package version: dpkg -l | grep onlyoffice-documentserver or rpm -qa | grep onlyoffice-documentserverAffected if The installed version is exactly 5.5.0
-
Confirm WebSocket API endpoint is accessibleAttempt to connect to the WebSocket API endpoint at /webeditor/websocket or /socket.io/ (the exact path depends on the deployment). This can be tested with a WebSocket client or by examining if port 8000 or the web server accepts WebSocket upgrade requests.Affected if The WebSocket API endpoint responds to connection requests without authentication
-
Verify DocID parameter is accepted via WebSocketSend a WebSocket message containing a DocID parameter to the endpoint. This requires a WebSocket client to craft and send a message with an arbitrary DocID value.Affected if The WebSocket API accepts and processes a DocID parameter without sanitizing special characters or using parameterized queries
If ONLYOFFICE Document Server version is exactly 5.5.0 AND the WebSocket API with the DocID parameter is exposed, the environment is vulnerable to CVE-2020-11537.
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.
From vendor dataUpgrade to a patched version of ONLYOFFICE Document Server that implements proper input validation and parameterized queries for the DocID parameter in the Websocket API endpoint.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-11537 — 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-2020-11537 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