ONLYOFFICE Docs Server Path Traversal Vulnerability (CVE-2021-3199)
Published Last modified In CISA KEV since Sources: CVE.org
What is affected, what to do
Directory traversal with remote code execution can occur in /upload in ONLYOFFICE Document Server before 5.6.3, when JWT is used, via a /.. sequence in an image upload parameter.
The vulnerability is being actively exploited; treat it as a priority. Update ONLYOFFICE Document Server to version 5.6.3. Immediate actions, mitigation and detection rules are in the runbook below.
- Affected
- ONLYOFFICE Document Server
lt *..5.6.3
- ONLYOFFICE Document Server
- Fixed in
- ONLYOFFICE Document Server
5.6.3
- ONLYOFFICE Document Server
Not sure whether and how you are affected? Ask a question about this vulnerability
Metrics
9.8
XIEM Effective CVSS
Highest available CVSS rating from NVD and vendor data.
Source: NVD, CVSS v3
9.8
CVSS v3
Severity Critical on the scale from 0 to 10.
Source: CVE.org
88.1 %
EPSS score
High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
Source: FIRST EPSS, percentile 99.77
Show all metrics
- Severity
- Critical
Priority (0–325)
The priority score is a consolidated metric that condenses several individual signals into a single, action-guiding ranking: technical severity (CVSS), exploitation likelihood (EPSS), known-exploited status (KEV) and the context of the affected asset. The aim is to answer the only truly important question in vulnerability management: what first?
Read in glossary- 228.63 Methodology
Exploit maturity
An exploit is code or a technique that specifically uses a concrete vulnerability to force unintended behaviour — such as executing code or escalating privileges. It is the tool that turns a theoretical flaw into a practical attack.
Read in glossary- actively exploited
XIEM Effective CVSS
XIEM® is the tiered managed-security operating model from NEOSEC and a registered trademark of NEOSEC GmbH. It extends classic SIEM — the central collection, normalisation and correlation of security-relevant events — with endpoint forensics, network visibility and deception technology, and consolidates them into three building tiers: Sentry, Orchestrate and Command.
Read in glossary- 9.8 Methodology
CVSS v3
CVSS is the globally established, open standard for assessing the technical severity of a vulnerability on a scale from 0 to 10. It describes how easily a flaw can be exploited and what damage it can cause — but not how likely its actual exploitation is. CVSS and the complementary EPSS deliberately answer different questions.
Read in glossary- 9.8
EPSS score
The EPSS score is the absolute model output for an individual vulnerability: the estimated probability of real-world exploitation within the next 30 days, expressed as a value between 0 and 1 (i.e. 0 % to 100 %). A score of 0.42 means „the model estimates a 42 % chance of real-world exploitation within 30 days“.
Read in glossary- 88.1 %
- High — model estimates ≥ 50% chance of real-world exploitation within 30 days.
EPSS percentile
The EPSS percentile is the relative position of a vulnerability within all EPSS-scored CVEs, expressed as a value between 0 and 1. A percentile of 0.90 means „this CVE has a higher EPSS score than 90 % of all other scored CVEs“. Unlike the EPSS score, it is not a probability — but a positioning within a ranking.
Read in glossary- 99.77
- Critical — this CVE ranks in the top fifth of all CVEs scored today (rank ≥ 80%).
KEV status
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- Actively exploited
- Published
In CISA KEV since
The KEV catalogue is a list maintained by the US authority CISA of vulnerabilities for which active exploitation in the wild has been confirmed. It answers not the question „how severe?“ but „is it already being attacked?“ — thereby sharply prioritising patching.
Read in glossary- CISA assessment (SSVC)
- Exploitation: active · automatable · Technical impact: total
- Source: CISA Vulnrichment, as of 8 October 2026
CWE
CWE is a catalogue of typical weakness types in software and hardware — such as flawed input validation, unsafe memory handling or poor authentication. Where a CVE names a concrete vulnerability in a concrete product, a CWE describes the underlying class of defect.
Read in glossary- CWE-22
Response and mitigation
Why act now?
Prioritisation rationale
This flaw is reachable over the network with no authentication and no user interaction, and yields full server compromise with high impact on confidentiality, integrity and availability; its exploitation likelihood sits among the highest of all scored CVEs. Document Server is usually internet-facing because end-user browsers talk to it directly, and it typically sits beside sensitive collaboration platforms such as Nextcloud or ownCloud with access to document stores — making it an attractive foothold for data theft and lateral movement. CISA does not flag known ransomware use, but that doesn't lower urgency: treat any externally reachable instance below 5.6.3 as critical and patch or take it offline now; internal-only instances should be fixed with high priority in the next maintenance window.
Runbook step 1
Immediate response (0-24 h)
- Inventory: Locate every ONLYOFFICE Document Server instance — package installs,
onlyoffice/documentserverDocker containers, and deployments backing Nextcloud/ownCloud/Seafile integrations — and record versions. Everything before 5.6.3 is vulnerable. - Patch: Upgrade to ONLYOFFICE Document Server 5.6.3 or later. Given how old the 5.6.x line is, go straight to the current supported release; check the vendor advisory/changelog for the exact target version.
- Cut exposure: If you can't patch within hours, pull Document Server off the internet or restrict it at the reverse proxy to known source ranges (VPN, corporate egress IPs) as a stopgap.
- Check for compromise before trusting the host: On vulnerable, exposed instances, review web logs for traversal requests to
/uploadand hunt for unexpected files outside the upload/cache directory (see detection). If you find hits, isolate, preserve evidence, and rebuild from a clean image rather than cleaning in place. - Rotate secrets: Regenerate the Document Server JWT secret (
local.json,services.CoAuthoring.secret) and the matching secret in every connector (Nextcloud, ownCloud, etc.). Also rotate any credentials stored on the host — database, RabbitMQ/Redis, storage back-ends.
- Inventory: Locate every ONLYOFFICE Document Server instance — package installs,
Runbook step 2
Mitigation layers
- Network segmentation: Place Document Server in a dedicated DMZ segment. Allow outbound traffic only to integration back-ends (callbacks and document fetches); block all other egress to frustrate reverse shells and tool staging.
- WAF/reverse-proxy rule: Reject requests to
/uploadwhose path or parameters contain traversal sequences, raw or encoded:/..,../,..%2f,%2e%2e,%252e,..\. nginx example:location ~* ^/upload { if ($request_uri ~* "(\.\.|%2e%2e|%252e)") { return 403; } }. Also enable ModSecurity/OWASP CRS rule group 930 (LFI/path traversal) in blocking mode for this vhost. - IPS signature: Deploy a Suricata/Snort rule matching normalised
http.urito/uploadcontaining/..on perimeter sensors; run it in alert mode first to confirm it doesn't trip on legitimate editor traffic. - Endpoint hardening: Run services as the unprivileged default user (
ds), remove write access to application and config directories, and run containers with a read-only root filesystem and without--privileged. Where feasible, apply an AppArmor/SELinux profile that prevents Node.js workers from spawning shells. - IAM/integrations: Use a strong, randomly generated JWT secret shared only between Document Server and its connector, and keep the list of trusted integration hosts minimal.
Runbook step 3
Detection rules
- Web/proxy logs: Requests to
/uploadwith traversal patterns. SPL:index=web uri_path="/upload*" (uri="*/..*" OR uri="*..%2f*" OR uri="*%2e%2e*") | stats count by src_ip, uri, status. Triage 2xx responses first. - EDR process ancestry: Document Server Node.js processes (
docservice,converter, userds) spawningsh,bash,curl,wget,pythonornc. Sigma shape:ParentImage|endswith: '/node'ANDUser: 'ds'ANDImage|endswith: ['/sh','/bash','/curl','/wget']. - Linux auditd / Sysmon for Linux (EID 11): File writes by
dsoutside the cache/upload path — especially into program directories, web roots, cron directories,~/.ssh/or systemd units. auditd:-w /etc/cron.d -p wa -k oo_persistand-a always,exit -F arch=b64 -S execve -F uid=<ds-uid> -k oo_exec. - Network telemetry (Zeek/Suricata): New outbound connections from the Document Server host to destinations other than the integration back-end or update servers, particularly right after
/uploadrequests; filter Zeekconn.logonid.orig_h == <docserver>for first-seenid.resp_h. - Integrity check: Compare installed files against the official package or image hashes;
docker diff <container>quickly surfaces modified files.
- Web/proxy logs: Requests to
Detection rules
No NEOSEC detection rule is available for this vulnerability yet.
Classification under NIS2 and CRA
Rule-based classification from exploitation status and severity. It does not replace a case-by-case assessment.
NIS2
NIS2 is EU Directive (EU) 2022/2555 to raise the level of cybersecurity across the Union. It substantially broadens obligations compared with the first NIS directive: more sectors, mandatory risk management, staged reporting duties and personal accountability of senior management.
Read in glossary- Actively exploited: treat the vulnerability as a priority in vulnerability handling under Art. 21(2)(e) NIS2. If it is exploited in your environment, check the reporting obligation under Art. 23 (early warning within 24 hours).
CRA
The CRA is EU Regulation (EU) 2024/2847 setting horizontal cybersecurity requirements for „products with digital elements“ — from industrial controllers and software to connected consumer devices. For the first time manufacturers must ensure security across the entire product lifecycle, handle vulnerabilities and provide security updates.
Read in glossary- Since 11.09.2026, manufacturers of affected products with digital elements must report actively exploited vulnerabilities under Art. 14 CRA, with an early warning within 24 hours via ENISA's single reporting platform.
ISO/IEC 27001
ISO/IEC 27001 is the internationally leading standard for an information security management system (ISMS). It describes a risk-based, process-oriented framework to systematically plan, implement, review and improve information security.
Read in glossary- Control A.8.8, management of technical vulnerabilities: assess relevance to your systems, plan remediation and keep evidence.
Description
Directory traversal with remote code execution can occur in /upload in ONLYOFFICE Document Server before 5.6.3, when JWT is used, via a /.. sequence in an image upload parameter.
Source: NVD (NIST), cvelistv5, CISA KEV Catalog
Affected products
The following versions are affected. Older releases of the same product line are also vulnerable unless stated otherwise.
| Affected versions | Fixed in | ||
|---|---|---|---|
| onlyoffice | document_server |
|
|
Vendors and products
Weakness classes (CWE)
CWE-22Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')
Base
The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory.
Entry at MITRE CWE-22
Public exploit references
Publicly reported proof-of-concepts, exploit modules and detection templates for this vulnerability. NEOSEC links to the original sources only and does not provide any exploit code.
| CISA KEV Catalog | CISA Known Exploited Vulnerability (opens in a new tab)cisa.gov | actively exploited |
References & sources
- github.comONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf…x_refsource_CONFIRM
- github.comnola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadIm…x_refsource_MISC
- github.commoehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFil…x_refsource_MISC
- cisa.govknown-exploited-vulnerabilities-catalog?field_cve=CVE-2021-3199government-resource
Changes to this CVE
Who changed this CVE and when: NVD (analysis, affected products, CVSS), the CVE publisher (CNA) and additional providers such as CISA (ADP).
NVD analysis modifiedNVD
Show the original change
Individual changes of this event as published by NVD Type Action Before After Reference type added —CISA-ADP: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-3199 Types: US Government ResourceSource identifier: nvd@nist.gov
Record modifiedCISA ADP
CISA assessment (SSVC): exploitation: active, automatable: yes
Show 2 original changes
Individual changes of this event as published by NVD Type Action Before After SSVC assessment removed {"id":"CVE-2021-3199","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-08T17:40:14.811565Z"}—SSVC assessment added —{"id":"CVE-2021-3199","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-08T00:00:00+00:00"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
CISA KEV entry updated9119a7d8…
4 individual changes: Date Added, Due Date, Required Action, Vulnerability Name
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After Date Added added —2026-10-08Due Date added —2026-10-08Required Action added —2026-10-08Vulnerability Name added —2026-10-08Source identifier: 9119a7d8-5eab-497f-8521-727c672e3725
Record modifiedMITRE
New references:Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.pyReference added —https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.pyReference added —https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563Reference removed https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.py—Reference removed https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.py—Reference removed https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563—Reference type removed https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.py Types: Exploit, Third Party Advisory—Reference type removed https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.py Types: Exploit, Third Party Advisory—Reference type removed https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563 Types: Release Notes, Third Party Advisory—Source identifier: cve@mitre.org
Record modifiedCISA ADP
CVSS V3.1: AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
CISA assessment (SSVC): exploitation: active, automatable: yes
Weakness type: CWE-22
Show 4 original changes
Individual changes of this event as published by NVD Type Action Before After CVSS added —AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:HWeakness type (CWE) added —CWE-22Reference added —https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2021-3199SSVC assessment added —{"id":"CVE-2021-3199","role":"CISA Coordinator","options":[{"exploitation":"active"},{"automatable":"yes"},{"technicalImpact":"total"}],"version":"2.0.3","timestamp":"2026-10-08T17:40:14.811565Z"}Source identifier: 134c704f-9b21-4f2e-91b3-4a467353bcc0
Show one older change
Record modifiedCVE Program
New references:Show 9 original changes
Individual changes of this event as published by NVD Type Action Before After Reference added —https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.pyReference added —https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.pyReference added —https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563Reference removed https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.py—Reference removed https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.py—Reference removed https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563—Reference type removed https://github.com/moehw/poc_exploits/tree/master/CVE-2021-3199/poc_uploadImageFile.py Types: Exploit, Third Party Advisory—Reference type removed https://github.com/nola-milkin/poc_exploits/blob/master/CVE-2021-3199/poc_uploadImageFile.py Types: Exploit, Third Party Advisory—Reference type removed https://github.com/ONLYOFFICE/DocumentServer/blob/903fe5ab7a275bd69c3c3346af2d21cf87ebeabf/CHANGELOG.md#563 Types: Release Notes, Third Party Advisory—Source identifier: af854a3a-2127-422b-91ae-364da2661108
Embed badge
Show the severity and KEV status of this vulnerability on your site – with a link back here. The image is updated hourly.
<a href="https://intel.neosec.eu/en/cve/CVE-2021-3199"><img src="https://intel.neosec.eu/badge/cve/CVE-2021-3199.svg?lang=en" alt="CVE-2021-3199 – NEOSEC Intel" height="20"></a>