WordPress plugin
BeeTeam368 Extensions security & vulnerabilities
Unpatched vulnerability in the latest version
At least one vulnerability affects the latest version and no fix has been released. Deactivate the plugin or restrict access to the affected feature until the vendor ships a patch.
- Critical0
- High3
- Medium0
- Low0
All BeeTeam368 Extensions vulnerabilities
| Severity | Vulnerability | CVE | Published |
|---|---|---|---|
| High8.1 | Unauthenticated Local File Inclusion ≤1.9.4No patch available | CVE-2025-25174 | |
| High8.8 | Authenticated (Subscriber+) Arbitrary File Upload ≤2.3.5Update to 2.3.6 | CVE-2025-6423 | |
| High8.8 | Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion ≤2.3.4Update to 2.3.5 | CVE-2025-6381 |
- High8.1Unauthenticated Local File Inclusion
≤1.9.4No patch available
- High8.8Authenticated (Subscriber+) Arbitrary File Upload
≤2.3.5Update to 2.3.6
- High8.8Authenticated (Subscriber+) Directory Traversal to Arbitrary File Deletion
≤2.3.4Update to 2.3.5
BeeTeam368 Extensions: common questions
Does BeeTeam368 Extensions have known vulnerabilities?
Yes. VulnCrest Radar lists 3 known vulnerabilities in BeeTeam368 Extensions: 3 high. At least one is not fixed in the latest version.
How do I check which version of BeeTeam368 Extensions I run?
In wp-admin open Plugins → Installed Plugins; the version is shown under the name. Without admin access, our passive Check my site tool can often read it from public files.
What is the most recent BeeTeam368 Extensions vulnerability?
CVE-2025-25174, published Jul 30, 2025: BeeTeam368 Extensions <= 1.9.4 - Unauthenticated Local File Inclusion. Severity: High (CVSS 8.1).
Is any BeeTeam368 Extensions vulnerability listed in CISA KEV?
No. None of the known BeeTeam368 Extensions vulnerabilities is currently listed in the CISA KEV catalog.