Overview
The BeeTeam368 Extensions Pro plugin for WordPress has been identified as vulnerable to a severe Directory Traversal exploit. This vulnerability, identified as CVE-2025-6379, affects all versions up to and including 2.3.4. As WordPress is a widely used content management system, the potential impact of this vulnerability is extensive and could lead to full system compromise or data leakage. This vulnerability is particularly concerning as it could be exploited by attackers with a low privilege level, such as Subscribers, highlighting the importance of immediate mitigation efforts.
Vulnerability Summary
CVE ID: CVE-2025-6379
Severity: High (CVSS: 8.8)
Attack Vector: Network
Privileges Required: Subscriber level
User Interaction: Required
Impact: System compromise, potential data leakage
Affected Products
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
BeeTeam368 Extensions Pro Plugin for WordPress | Up to and including 2.3.4
How the Exploit Works
The vulnerability resides in the handle_live_fn() function of the BeeTeam368 Extensions Pro plugin for WordPress. A flaw in this function allows authenticated users to perform actions on files outside of the originally intended directory, a type of attack known as Directory Traversal. This flaw can be exploited by attackers to delete the wp-config.php file, a critical file for WordPress site functions. By deleting this file, attackers could potentially take over the website, leading to severe impacts such as data leakage or system compromise.
Conceptual Example Code
The following conceptual example demonstrates how an attacker might exploit this vulnerability. This code is a simplified representation and not a working exploit:
POST /wp-admin/admin-ajax.php?action=bt_handle_live_fn HTTP/1.1
Host: target.example.com
Content-Type: application/x-www-form-urlencoded
file=../../../../../wp-config.php&cmd=deleteIn this example, the attacker attempts to delete the wp-config.php file by manipulating the file parameter in the POST request to traverse directories upwards and target the wp-config.php file.
Mitigation Guidance
To mitigate this vulnerability, users of BeeTeam368 Extensions Pro plugin for WordPress should apply the latest vendor patch as soon as possible. As a temporary solution, implementing a Web Application Firewall (WAF) or Intrusion Detection System (IDS) can provide an additional layer of protection. However, these solutions should not replace the need for patching, as they may not completely prevent exploitation of the vulnerability.