Ameeba Security Research

Defensive CVE and exploit intelligence

Ameeba Blog Search
TRENDING · 1 WEEK
Attack Vector
Vendor
Severity

CVE-2025-6380: Privilege Escalation Vulnerability in ONLYOFFICE Docs Plugin for WordPress

Views: 667

Overview

The cybersecurity landscape faces a new threat in the form of a severe vulnerability in the ONLYOFFICE Docs plugin for WordPress. The vulnerability, identified as CVE-2025-6380, potentially affects a vast number of websites using the ONLYOFFICE Docs plugin, ranging from versions 1.1.0 to 2.2.0. The severity of this vulnerability lies in the fact that it allows unauthenticated attackers to perform privilege escalation, potentially leading to system compromise and data leakage.

Vulnerability Summary

CVE ID: CVE-2025-6380
Severity: Critical (9.8 out of 10)
Attack Vector: Network
Privileges Required: None
User Interaction: None
Impact: Potential system compromise and data leakage

Affected Products

Ameeba Chat Icon Share secrets securely

Ameeba is private infrastructure for communication and sensitive work built on encrypted identity instead of exposed corporate identity systems.

Passwords, credentials, confidential files, screenshots, internal discussions, sensitive AI context, and private coordination should not become exposed across ordinary communication platforms.

  • • Encrypted identity
  • • Private Spaces for organizations and teams
  • • End-to-end encrypted chat, calls, files, and notes
  • • Sensitive AI work and protected collaboration
  • • Built for information that cannot leak

Our mission is to secure human work alongside AI.

Product | Affected Versions

ONLYOFFICE Docs Plugin for WordPress | 1.1.0 – 2.2.0

How the Exploit Works

The vulnerability arises from a lack of proper authorization in the oo.callback REST endpoint of the ONLYOFFICE Docs plugin for WordPress. The plugin’s permission callback checks that the supplied, encrypted attachment ID maps to an existing attachment post. However, it does not verify the identity or capabilities of the requester. This oversight allows unauthenticated attackers to log in as any user, escalating their privileges and potentially gaining unauthorized access to sensitive information or control over the system.

Conceptual Example Code

The following is a conceptual example of how an attacker might exploit this vulnerability. In this case, the attacker sends a malicious HTTP request to the vulnerable endpoint:

POST /wp-json/onlyoffice/v1/callback HTTP/1.1
Host: target.example.com
Content-Type: application/json
{
"attachment": {
"id": "<encrypted_attachment_id>",
"userid": "<arbitrary_user_id>"
}
}

In this example, `` is a valid encrypted attachment ID, and `` is the user ID of the victim. This request could potentially allow the attacker to log in as the victim, leading to unauthorized access and potential data leakage.

Mitigation and Prevention

To mitigate this vulnerability, affected users are advised to apply the vendor’s patch as soon as possible. If the patch cannot be applied immediately, the use of a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can serve as a temporary mitigation strategy. Regularly updating all software and plugins to their latest versions can help prevent future vulnerabilities.

Want to discuss this further? Join the Ameeba Cybersecurity Group Chat.

Disclaimer:

The information and code presented in this article are provided for educational and defensive cybersecurity purposes only. Any conceptual or pseudocode examples are simplified representations intended to raise awareness and promote secure development and system configuration practices.

Do not use this information to attempt unauthorized access or exploit vulnerabilities on systems that you do not own or have explicit permission to test.

Ameeba and its authors do not endorse or condone malicious behavior and are not responsible for misuse of the content. Always follow ethical hacking guidelines, responsible disclosure practices, and local laws.

More posts

Ameeba Chat