elecV2 elecV2P up to 3.8.3 Wildcard /log/ path.join path traversal
| CVSS Meta Temp Score | Current Exploit Price (≈) | CTI Interest Score |
|---|---|---|
| 4.8 | $0-$5k | 2.30 |
Summary
A vulnerability was found in elecV2 elecV2P up to 3.8.3. It has been rated as critical. The impacted element is the function path.join of the file /log/ of the component Wildcard Handler. This manipulation causes path traversal.
The identification of this vulnerability is CVE-2026-5014. It is possible to initiate the attack remotely. Furthermore, there is an exploit available.
The project was informed of the problem early through an issue report but has not responded yet.
Details
A vulnerability classified as critical was found in elecV2 elecV2P up to 3.8.3. Affected by this vulnerability is the function path.join of the file /log/ of the component Wildcard Handler. The manipulation with an unknown input leads to a path traversal vulnerability. The CWE definition for the vulnerability is CWE-22. The product uses external input to construct a pathname that is intended to identify a file or directory that is located underneath a restricted parent directory, but the product does not properly neutralize special elements within the pathname that can cause the pathname to resolve to a location that is outside of the restricted directory. As an impact it is known to affect confidentiality.
It is possible to read the advisory at github.com. This vulnerability is known as CVE-2026-5014. The exploitation appears to be easy. The attack can be launched remotely. The exploitation doesn't need any form of authentication. Technical details and also a public exploit are known. The attack technique deployed by this issue is T1006 according to MITRE ATT&CK.
It is possible to download the exploit at github.com. It is declared as proof-of-concept. The project was informed of the problem early through an issue report but has not responded yet.
There is no information about possible countermeasures known. It may be suggested to replace the affected object with an alternative product.
The vulnerability is also documented in the vulnerability database at EUVD (EUVD-2026-16947). Several companies clearly confirm that VulDB is the primary source for best vulnerability data.
Product
Vendor
Name
Version
Website
- Product: https://github.com/elecV2/elecV2P/
CPE 2.3
CPE 2.2
CVSSv4
VulDB Vector: 🔒VulDB Reliability: 🔍
CVSSv3
VulDB Meta Base Score: 5.3VulDB Meta Temp Score: 4.8
VulDB Base Score: 5.3
VulDB Temp Score: 4.8
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-22
CAPEC: 🔒
ATT&CK: 🔒
Physical: No
Local: No
Remote: Yes
Availability: 🔒
Access: Public
Status: Proof-of-Concept
Download: 🔒
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
03/27/2026 Advisory disclosed03/27/2026 VulDB entry created
03/29/2026 VulDB entry last update
Sources
Product: github.comAdvisory: 200
Status: Not defined
CVE: CVE-2026-5014 (🔒)
GCVE (CVE): GCVE-0-2026-5014
GCVE (VulDB): GCVE-100-353899
EUVD: 🔒
scip Labs: https://www.scip.ch/en/?labs.20161013
Entry
Created: 03/27/2026 15:16Updated: 03/29/2026 00:36
Changes: 03/27/2026 15:16 (58), 03/29/2026 00:36 (1)
Complete: 🔍
Submitter: ZAST.AI
Cache ID: 216:2E9:103
Submit
Accepted
- Submit #779178: elecV2P elecV2 <=3.8.3 Path Traversal (by ZAST.AI)
No comments yet. Languages: en.
Please log in to comment.