Vulnerabilities

Vulnerability · CVE-2025-6381

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.

Published Jun 28, 2025 · catalog updated Apr 8, 2026 · BeeTeam368 Extensions

Check this week

CVE-2025-6381 is not in CISA KEV. FIRST estimates a 74.00% chance of exploitation in the next 30 days. Check whether you run BeeTeam368 Extensions.

Gaps on this record

  • No vendor fix or required action is stored. Compare the linked advisory before you change production.
Severity
High8.8
Known exploitation
Not in CISA/VulnCheck KEV
EPSS
74.00%
Remediation
Vendor / distro source
Affected products
vendor beeteam368 BeeTeam368 Extensions 0 ≤2.3.4

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.

Are you affected?

Enter the version you run. The result uses only the ranges stored on this record.

The check returns affected, not affected, or incomplete. It does not guess a version that is missing from the record.

  • vendor beeteam368 BeeTeam368 Extensions 0 ≤2.3.40 ≤2.3.4

How to fix CVE-2025-6381

What to do

Three questions, each answered from this record only. Confirm the vendor advisory before you patch.

Should you patch?

CVE-2025-6381 is not in CISA KEV. FIRST estimates a 74.00% chance of exploitation in the next 30 days. Check whether you run BeeTeam368 Extensions.

Which versions are affected?

Compare what you have installed with beeteam368 BeeTeam368 Extensions 0 ≤2.3.4 0 ≤2.3.4. Compare the installed version with the linked vendor advisory before you change production.

What should an analyst verify?

No weakness class is stored. EPSS 74.00%. There is no CISA KEV listing. No Exploit-DB or Metasploit reference is linked. Use the source links for the original advisory.

Technology hubs

Code

The project this record applies to. Exploit listings stay in References.

No public source repository is identified for this product.

Timeline

Detection, updates, and resolution for this record.

  1. Jun 28, 2025 · EUVD

    Detected

    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 fil

  2. Apr 8, 2026 · EUVD

    Updated

    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 fil

Sources

  • CVE.orgVulnerability recordCVE-2025-6381

    Official CVE identifier

    cve.org
  • EUVDVulnerability recordEUVD-2025-28733

    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 actio

    euvd.enisa.europa.eu

References

Freshness

Last verified in this catalog Apr 8, 2026. Significant claims (KEV, EPSS, CVSS, affected ranges) come from the source rows above — open the original publisher for the authoritative advisory.