# CVE-2026-5014: elecV2 elecV2P Wildcard log path.join path traversal

> Remote attackers can exploit a path traversal vulnerability in the Wildcard Handler to read arbitrary files from the server.

- **Severity:** Medium 6.9 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N/E:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Mar 2026
- **Updated:** 30 Mar 2026
- **Also known as:** GHSA-72rh-qqpc-g693

## What is CVE-2026-5014?

CVE-2026-5014 is a medium-severity path traversal vulnerability in elecV2P, published on 28 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

A vulnerability was found in elecV2 elecV2P up to 3.8.3. The affected element is the function path.join of the file /log/ of the component Wildcard Handler. The manipulation results in path traversal. The attack may be performed from remote. The exploit has been made public and could be used. The project was informed of the problem early through an issue report but has not responded yet.

Weakness: CWE-22 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-5014?


## How do I fix CVE-2026-5014?

No fix has been published for CVE-2026-5014 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-5014 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5014 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-5014 and fix it if it is affected.

What it is: CVE-2026-5014 is a medium-severity path traversal vulnerability in elecV2P, published on 28 Mar 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-5014 exists.

Affected product: elecV2P. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-5014/ (Markdown: https://insights.sbomify.com/CVE-2026-5014/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-5014
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-5014
- OSV: https://osv.dev/vulnerability/CVE-2026-5014

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-5014/
Summaries are generated and may contain mistakes; the official description above is the record.