CVE-2026-5016
Received Received - Intake
Server-Side Request Forgery in elecV2 URL Handler

Publication date: 2026-03-28

Last updated on: 2026-04-29

Assigner: VulDB

Description
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.
CVSS Scores
EPSS Scores
Probability:
Percentile:
Meta Information
Published
2026-03-28
Last Modified
2026-04-29
Generated
2026-05-27
AI Q&A
2026-03-29
EPSS Evaluated
2026-05-25
NVD
EUVD
Affected Vendors & Products
Showing 1 associated CPE
Vendor Product Version / Range
elecv2 elecv2p to 3.8.3 (inc)
Helpful Resources
Exploitability
CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-918 The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?

This vulnerability exists in elecV2 elecV2P up to version 3.8.3, specifically in the function eAxios within the /mock file of the URL Handler component.

The issue arises from manipulation of the argument 'req', which leads to server-side request forgery (SSRF).

An attacker can exploit this vulnerability remotely, and the exploit is publicly available.

The project was informed early via an issue report but has not yet responded.


How can this vulnerability impact me? :

This vulnerability allows an attacker to perform server-side request forgery (SSRF), which means they can make the server send requests to unintended locations.

Such an attack can lead to unauthorized access to internal systems, data exposure, or interaction with internal services that are not normally accessible.

Because the exploit is publicly available and can be launched remotely without authentication, the risk of exploitation is significant.


Ask Our AI Assistant
Need more information? Ask your question to get an AI reply (Powered by our expertise)
0/70
EPSS Chart