CVE-2026-5014
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceA path traversal vulnerability in elecV2P's wildcard handler for /log/ files allows remote attackers to manipulate the path.join function to access files outside the intended directory. The vulnerability exists in version 3.8.3 and earlier, and a public exploit is available.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify if elecV2P is runningCheck for running processes or services named 'elecv2p' or listen on ports commonly used by elecV2P (default: 80, 443, 8000). Use commands like 'ps aux | grep elecv2p' or 'netstat -tlnp' to find the service.Affected if elecV2P service is found running in the environment
-
Determine installed versionCheck the version file or package.json in the elecV2P installation directory. Common paths include /opt/elecv2p/, ~/elecv2p/, or the directory where the application was installed. Run 'cat version' or 'cat package.json | grep version' in the installation folder.Affected if Version is 3.8.3 or earlier
-
Verify /log/ endpoint is accessibleTest if the /log/ wildcard endpoint is exposed by making an HTTP request to the elecV2P server. Attempt accessing a basic path like /log/test.log and check for a response.Affected if The /log/ endpoint responds to HTTP requests (service is network-accessible)
-
Confirm path traversal vulnerability existsCompare your findings: if elecV2P is running, version 3.8.3 or earlier is installed, and the /log/ endpoint is accessible, then the environment contains the vulnerable configuration.Affected if All three conditions are true: elecV2P is running, version 3.8.3 or earlier, and /log/ endpoint is network-accessible
You are affected if elecV2P version 3.8.3 or earlier is running with the /log/ endpoint accessible over the network.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataImplement strict input validation and canonicalization on path.join calls to prevent directory traversal; restrict file access to the intended /log/ directory boundaries, and update to a patched version once released.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5014 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5014 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data