ONLYOFFICE Docs 1.1.0 - 2.2.0 - Missing Authorization to Unauthenticated Privilege Escalation via callback Function
Strategic Overview
- Status
- Patched in 2.3.0
- Affected Plugin
- ONLYOFFICE Docs
- Affected Version
1.1.0 – 2.2.0- CVSS
- 9.8Critical
- Weakness type
- CWE-862 · Missing Authorization
- CVE
CVE-2025-6380
At a glance
CVE-2025-6380 is a critical-severity Missing Authorization vulnerability in the ONLYOFFICE Docs WordPress plugin, affecting versions 1.1.0 – 2.2.0. It carries a CVSS score of 9.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires no authentication. The issue is fixed in version 2.3.0; sites on affected versions should update now. Disclosed July 2025, reported by kr0d.
Vulnerability Overview
The ONLYOFFICE Docs plugin for WordPress is vulnerable to Privilege Escalation due to missing authorization within its oo.callback REST endpoint in versions 1.1.0 to 2.2.0. The plugin’s permission callback only verifies that the supplied, encrypted attachment ID maps to an existing attachment post, but does not verify the requester’s identity or capabilities. This makes it possible for unauthenticated attackers to log in as an arbitrary user.
Technical Analysis
The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no privileges on the target site, and no interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.
CWE-862: Missing Authorization
Reaching this weakness in ONLYOFFICE Docs 1.1.0 – 2.2.0 takes no account at all. A missing authorization check means a function is reachable by anyone who can reach the endpoint, because the code never asks whether the caller is allowed to perform the action.
Any user who can reach the endpoint gets to run an action reserved for higher-privileged roles, from reading protected data to changing settings or content. For ONLYOFFICE Docs the fix is 2.3.0: builds 1.1.0 – 2.2.0 are affected, anything from 2.3.0 onward is not.
Remediation
Update to version 2.3.0, or a newer patched version
How does WordSec protect against this?
This one needs no account at all, which puts it outside what login hardening can reach; WordSec's login security narrows the account-level paths around it, and the firewall is what inspects the request itself. None of that substitutes for the fix: ONLYOFFICE Docs 2.3.0 closes this, and updating the plugin is the step that ends it.
- Login Security
- Alerts
External References
Related records
Other vulnerabilities in ONLYOFFICE Docs
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C