Beeteam368 develops the Vidmov product, a narrowly scoped offering where the observed vulnerability signal centers on path-traversal issues, including both absolute path traversal and improper pathname restriction weaknesses. These flaws reflect input-handling gaps in file-access logic and represent a recurrent structural exposure pattern for this vendor. Current severity, exploitation, and disclosure counts are shown alongside this summary.
The number and severity of CVEs published that impact products developed by Beeteam368 over time
Signals from CVEs in this vendor scope (4 CVEs).
4 CVEs · Highest risk first
| CVE | Published | CVSS | Risk | KEV | Exploit |
|---|---|---|---|---|---|
CVE-2025-25172HIGH Improper Control of Filename for Include/Require Statement in PHP Program ('PHP Remote File Inclusion') vulnerability in beeteam368 VidMov vidmov allows PHP Local File Inclusion.Th | Aug 14, 2025 | 8.1 | 26 | NO | NO |
CVE-2025-6381HIGH 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 mak | Jun 28, 2025 | 8.8 | 26 | NO | NO |
CVE-2025-6379HIGH The BeeTeam368 Extensions Pro plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 2.3.4 via the handle_live_fn() function. This makes it | Jun 28, 2025 | 8.8 | 26 | NO | NO |
CVE-2025-67914HIGH Path Traversal: '.../...//' vulnerability in beeteam368 VidMov vidmov allows Path Traversal.This issue affects VidMov: from n/a through <= 2.3.8. | Jan 8, 2026 | 7.7 | 24 | NO | NO |
Signals from CVEs in this vendor scope (4 CVEs).
An overview of all social media posts that mention a CVE ID that affects a product developed by Beeteam368.
Media articles that mention a CVE ID that affects a product developed by Beeteam368 — matched by CVE ID, not by vendor name.