Which versions of Elecv2P are affected by CVE-2026-5016?

elecV2P versions up to 3.8.3 contain an unauthenticated Server-Side Request Forgery vulnerability that allows remote attackers to manipulate internal HTTP requests and access confidential resources…

Is there a public PoC exploit available for CVE-2026-5016?

Yes, a public proof-of-concept exploit is available for CVE-2026-5016. Prioritise patching immediately. EPSS: 0.0%.

How to fix or mitigate CVE-2026-5016?

Within 24 hours: Audit all systems running elecV2P and document current versions; disable or restrict network access to elecV2P instances via firewall rules or network segmentation. Within 7 days: Upgrade to elecV2P version 3.8.4 or later if available, or evaluate alternative solutions; if upgrade impossible, implement Web Application Firewall rules to block suspicious /mock URL handler requests. Within 30 days: Complete migration to patched version or replacement product; conduct forensic review of access logs for evidence of exploitation.

Elecv2P CVE-2026-5016

Q: What is the CVSS score of CVE-2026-5016?

CVE-2026-5016 has a CVSS 4.0 base score of 5.5 (Medium). CVSS vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X. EPSS exploitation probability: 0.0%.

EUVD-2026-16951 MEDIUM

Server-Side Request Forgery (SSRF) (CWE-918)

2026-03-28 VulDB

SSRF Elecv2P Elecv2

5.5

CVSS 4.0 · NVD

Severity by source

NVD PRIMARY

5.5 MEDIUM

CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Lifecycle Timeline

CVSS changed

Apr 29, 2026 - 01:11 NVD

6.9 (MEDIUM) 5.5 (MEDIUM)

PoC Detected

Mar 30, 2026 - 13:26 vuln.today

Public exploit code

EUVD ID Assigned

Mar 28, 2026 - 22:00 euvd

EUVD-2026-16951

Analysis Generated

Mar 28, 2026 - 22:00 vuln.today

CVE Published

Mar 28, 2026 - 21:45 nvd

MEDIUM 6.9

DescriptionCVE.org

A 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.

AnalysisAI

Server-Side Request Forgery (SSRF) in elecV2P versions up to 3.8.3 allows unauthenticated remote attackers to manipulate internal or external HTTP requests via the eAxios function in the /mock URL handler. The vulnerability enables unauthorized access to internal resources, data exfiltration from confidential endpoints, and potential lateral movement within internal networks. Publicly available exploit code exists (GitHub issue #202), significantly lowering the barrier to exploitation. EPSS data not provided, but the combination of network-accessible attack vector, low complexity, no authentication requirement, and public POC represents elevated real-world risk. Vendor has not responded to early disclosure.

Technical ContextAI

This SSRF vulnerability (CWE-918) affects elecV2P, a JavaScript-based automation and request proxy tool, specifically in the eAxios HTTP client function within the mock URL handler endpoint. The flaw allows attackers to craft malicious requests that cause the server to make unauthorized HTTP requests to arbitrary destinations, including internal network resources not directly accessible from the internet. The affected component processes user-supplied URLs without proper validation or allowlist enforcement, enabling attackers to abuse the server's trust relationships and network position. CPE identifier cpe:2.3:a:elecv2:elecv2p indicates this affects the elecV2 vendor's elecV2P product across all platforms through version 3.8.3. SSRF vulnerabilities are particularly dangerous in cloud environments and containerized deployments where metadata services (e.g., AWS EC2 instance metadata at 169.254.169.254) or internal APIs may expose sensitive credentials and configuration data.

RemediationAI

No vendor-released patch identified at time of analysis as the project maintainer has not responded to the early disclosure reported via GitHub issue #202. Until an official patch is available, implement the following mitigations: (1) Deploy network-level controls to restrict elecV2P's outbound HTTP request capabilities using egress filtering, allowing only explicitly required external destinations and blocking RFC 1918 private address ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), localhost (127.0.0.0/8), link-local addresses (169.254.0.0/16), and cloud metadata endpoints. (2) If the /mock endpoint functionality is not required for operations, disable or remove access to this component entirely through reverse proxy rules or application configuration. (3) Implement Web Application Firewall (WAF) rules to inspect and validate URL parameters submitted to the /mock endpoint, rejecting requests containing internal IP addresses, localhost references, or cloud metadata service URLs. (4) Monitor the official GitHub repository (https://github.com/elecV2/elecV2P/) and VulDB entry (https://vuldb.com/vuln/353901) for vendor response and patch availability. Consider migrating to alternative automation tools if vendor responsiveness does not improve, as unmaintained software presents ongoing security risk.