Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2025-6380: CWE-862 Missing Authorization in onlyoffice ONLYOFFICE Docs

0
Critical
VulnerabilityCVE-2025-6380cvecve-2025-6380cwe-862
Published: Thu Jul 24 2025 (07/24/2025, 09:22:17 UTC)
Source: CVE Database V5
Vendor/Project: onlyoffice
Product: ONLYOFFICE Docs

Description

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.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 02/26/2026, 15:32:38 UTC

Technical Analysis

CVE-2025-6380 is a critical security vulnerability identified in the ONLYOFFICE Docs plugin for WordPress, specifically affecting versions 1.1.0 through 2.2.0. The root cause is a missing authorization check in the oo.callback REST API endpoint. This endpoint is designed to handle callbacks related to encrypted attachment IDs. However, the plugin's permission callback only verifies that the encrypted attachment ID maps to an existing attachment post, without validating the identity or capabilities of the requester. Consequently, an unauthenticated attacker can exploit this flaw to impersonate any user by supplying a valid encrypted attachment ID, effectively escalating privileges without authentication or user interaction. This vulnerability is classified under CWE-862 (Missing Authorization) and has a CVSS v3.1 base score of 9.8, reflecting its critical impact on confidentiality, integrity, and availability. The vulnerability allows attackers to gain unauthorized access to user accounts, potentially leading to data theft, unauthorized document modifications, or disruption of services. Although no active exploits have been reported in the wild, the ease of exploitation and the severity of impact make this a high-risk vulnerability. The lack of patches at the time of publication necessitates immediate attention from organizations using ONLYOFFICE Docs in WordPress environments.

Potential Impact

The impact of CVE-2025-6380 is severe for organizations using ONLYOFFICE Docs integrated with WordPress. An attacker can gain unauthorized access to arbitrary user accounts without authentication, leading to full compromise of user data and permissions. This can result in unauthorized disclosure of sensitive documents, unauthorized modifications or deletions of content, and potential disruption of document collaboration workflows. The breach of confidentiality and integrity can damage organizational reputation, lead to regulatory compliance violations, and cause operational downtime. Since the vulnerability affects a widely used document collaboration plugin, organizations relying on ONLYOFFICE Docs for internal or external document management are at significant risk. The vulnerability's network-exploitable nature and lack of required user interaction increase the likelihood of automated attacks or mass exploitation attempts once public exploit code becomes available.

Mitigation Recommendations

To mitigate CVE-2025-6380, organizations should immediately upgrade ONLYOFFICE Docs WordPress plugin to a version where the vulnerability is patched once available. Until a patch is released, implement the following specific mitigations: 1) Restrict access to the oo.callback REST endpoint by applying web application firewall (WAF) rules that block unauthenticated requests or requests from untrusted IP addresses. 2) Disable or limit the use of the ONLYOFFICE Docs plugin if feasible, especially on publicly accessible WordPress sites. 3) Monitor web server and application logs for suspicious access patterns targeting the oo.callback endpoint or unusual attachment ID requests. 4) Enforce strict WordPress user role and capability management to minimize the impact of compromised accounts. 5) Consider isolating ONLYOFFICE Docs functionality behind VPN or internal networks to reduce exposure. 6) Educate administrators and users about the risk and encourage vigilance for unusual account activity. These targeted mitigations go beyond generic advice by focusing on access control and monitoring specific to the vulnerable endpoint.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.1
Assigner Short Name
Wordfence
Date Reserved
2025-06-19T18:35:39.626Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6881fdd8ad5a09ad0033bed0

Added to database: 7/24/2025, 9:33:12 AM

Last enriched: 2/26/2026, 3:32:38 PM

Last updated: 3/21/2026, 2:43:53 AM

Views: 86

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses