CVE-2025-6381

BeeTeam368 Extensions <= 2.3.4 - Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion

2025-06-27 14:26
Tonn

Strategic Overview

Status
Patched in 2.3.5
Affected Plugin
BeeTeam368 Extensions
Affected Version
<= 2.3.4
CVSS
8.8High
Weakness type
CWE-36 · Absolute Path Traversal
CVE
CVE-2025-6381
View all BeeTeam368 Extensions vulnerabilities

At a glance

CVE-2025-6381 is a high-severity Absolute Path Traversal vulnerability in the BeeTeam368 Extensions WordPress plugin, affecting versions <= 2.3.4. It carries a CVSS score of 8.8 (reachable over the network; low attack complexity; high confidentiality, integrity, availability impact). Exploitation requires an authenticated account at Subscriber level or above. The issue is fixed in version 2.3.5; sites on affected versions should update now. Disclosed June 2025, reported by Tonn.

Vulnerability Overview

The BeeTeam368 Extensions plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.3.4 via the handle_remove_temp_file() function. This makes it possible for authenticated attackers, with Subscriber-level access and above, to perform actions on files outside of the originally intended directory. This vulnerability can be used to delete the wp-config.php file, which can be leveraged into a site takeover.

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 interaction from a victim user. A successful exploit has high impact on confidentiality, integrity, availability — full site compromise territory.

CWE-36: Absolute Path Traversal

The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize absolute path sequences such as /abs/path that can resolve to a location that is outside of that directory.

Remediation

Update to version 2.3.5, or a newer patched version

How does WordSec protect against this?

An attacker needs Subscriber access first, so the firewall sees the attempt as traffic from a logged-in account: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: BeeTeam368 Extensions 2.3.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C