beeteam368 VidMov Plugin up to 2.3.8 on WordPress path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 6.1 | $0-$5k | 0.00 |
Summary
A vulnerability identified as critical has been detected in beeteam368 VidMov Plugin up to 2.3.8 on WordPress. The impacted element is an unknown function. Performing a manipulation results in path traversal. This vulnerability was named CVE-2025-67914. The attack may be initiated remotely. There is no available exploit.
Details
A vulnerability classified as critical has been found in beeteam368 VidMov Plugin up to 2.3.8 on WordPress. This affects some unknown functionality. The manipulation with an unknown input leads to a path traversal vulnerability. CWE is classifying the issue as CWE-35. The product uses external input to construct a pathname that should be within a restricted directory, but it does not properly neutralize '.../...//' (doubled triple dot slash) sequences that can resolve to a location that is outside of that directory. This is going to have an impact on confidentiality, integrity, and availability. The summary by CVE is:
Path Traversal: '.../...//' vulnerability in beeteam368 VidMov vidmov allows Path Traversal.This issue affects VidMov: from n/a through <= 2.3.8.
The weakness was presented by Denver Jackson. It is possible to read the advisory at vdp.patchstack.com. This vulnerability is uniquely identified as CVE-2025-67914 since 12/15/2025. The exploitability is told to be easy. It is possible to initiate the attack remotely. The technical details are unknown and an exploit is not publicly available. The pricing for an exploit might be around USD $0-$5k at the moment (estimation calculated on 01/08/2026). The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
Product
Type
Vendor
Name
Version
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 6.3VulDB Meta Temp Score: 6.1
VulDB Base Score: 6.3
VulDB Temp Score: 6.1
VulDB Vector: 🔒
VulDB Reliability: 🔍
CVSSv2
| AV | AC | Au | C | I | A |
|---|---|---|---|---|---|
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| 💳 | 💳 | 💳 | 💳 | 💳 | 💳 |
| Vector | Complexity | Authentication | Confidentiality | Integrity | Availability |
|---|---|---|---|---|---|
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
| Unlock | Unlock | Unlock | Unlock | Unlock | Unlock |
VulDB Base Score: 🔒
VulDB Temp Score: 🔒
VulDB Reliability: 🔍
Exploiting
Class: Path traversalCWE: CWE-35 / CWE-23 / CWE-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Status: Not defined
EPSS Score: 🔒
EPSS Percentile: 🔒
Price Prediction: 🔍
Current Price Estimation: 🔒
| 0-Day | Unlock | Unlock | Unlock | Unlock |
|---|---|---|---|---|
| Today | Unlock | Unlock | Unlock | Unlock |
Threat Intelligence
Interest: 🔍Active Actors: 🔍
Active APT Groups: 🔍
Countermeasures
Recommended: no mitigation knownStatus: 🔍
0-Day Time: 🔒
Timeline
12/15/2025 CVE reserved01/08/2026 Advisory disclosed
01/08/2026 VulDB entry created
01/08/2026 VulDB entry last update
Sources
Advisory: vdp.patchstack.comResearcher: Denver Jackson
Status: Not defined
CVE: CVE-2025-67914 (🔒)
GCVE (CVE): GCVE-0-2025-67914
GCVE (VulDB): GCVE-100-340083
Entry
Created: 01/08/2026 12:22Changes: 01/08/2026 12:22 (54)
Complete: 🔍
Cache ID: 216::103
Statistical analysis made it clear that VulDB provides the best quality for vulnerability data.
No comments yet. Languages: en.
Please log in to comment.