CVE-2026-5016
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 identified in elecV2 elecV2P up to 3.8.3. This affects the function eAxios of the file /mock of the component URL Handler. Such manipulation of the argument req leads to server-side request forgery. It is possible to launch the attack remotely. The exploit is publicly available and might 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 confidenceAn SSRF vulnerability exists in elecV2P up to v3.8.3 where the eAxios function in the /mock endpoint (URL Handler component) lacks proper validation of the req argument, allowing remote attackers to make the server perform arbitrary HTTP requests to internal or external resources.
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
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
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 elecV2P installation and versionLocate the elecV2P installation directory and check the version file, or run 'elecv2p --version' if available. Common locations include /opt/elecv2p, ~/elecv2p, or the directory where the service was installed.Affected if The installed version is v3.8.3 or any earlier version (e.g., v3.8.2, v3.8.1, v3.8.0, etc.).
-
Verify /mock endpoint is accessibleCheck if the /mock endpoint is enabled in the elecV2P configuration. Review the server configuration file (typically config.json or similar) for endpoint routing settings, or attempt a GET request to http://<host>:<port>/mock to see if it responds.Affected if The /mock endpoint is exposed and responds to requests without requiring authentication or additional validation.
-
Confirm eAxios function availabilityReview the URL Handler component to verify the eAxios function is loaded and available. Check the installed modules or source code for the presence of the eAxios function in the /mock endpoint handler.Affected if The eAxios function exists in the URL Handler component and is accessible through the /mock endpoint.
-
Check network access to /mock endpointReview firewall rules, access control lists, or proxy settings to determine if the /mock endpoint can be reached by untrusted network sources. Verify whether the service binds to 0.0.0.0 or only localhost.Affected if The /mock endpoint is reachable from network segments that should not have access, or the service is exposed to the internet without authentication.
You are affected if elecV2P v3.8.3 or earlier is installed, the /mock endpoint is accessible, and the eAxios function is available in the URL Handler component - all three conditions must be true for the SSRF vulnerability to be exploitable.
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 dataUpdate to a patched version when available; until then, disable or restrict access to the /mock endpoint and implement network segmentation/firewall rules to limit outbound server connections.
- 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-5016 — 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-5016 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