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

Organizations using elecV2 elecV2P should be aware of notable risk from CVE-2026-5012, a OS command injection vulnerability rated CVSS 6.9.

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

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

How to fix or mitigate CVE-2026-5012?

Within 30 days: Identify affected systems running elecV2 elecV2P and apply vendor patches as part of regular patch cycle. Validate input sanitization for user-controlled parameters.

Elecv2P CVE-2026-5012

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

CVE-2026-5012 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: 1.0%.

EUVD-2026-16943 MEDIUM

OS Command Injection (CWE-78)

2026-03-28 VulDB

Command Injection 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 - 19:30 euvd

EUVD-2026-16943

Analysis Generated

Mar 28, 2026 - 19:30 vuln.today

CVE Published

Mar 28, 2026 - 19:15 nvd

MEDIUM 6.9

DescriptionCVE.org

A flaw has been found in elecV2 elecV2P up to 3.8.3. This issue affects the function pm2run of the file /rpc. Executing a manipulation can lead to os command injection. The attack can be executed remotely. The exploit has been published and may be used. The project was informed of the problem early through an issue report but has not responded yet.

AnalysisAI

Operating system command injection in elecV2P up to version 3.8.3 allows unauthenticated remote attackers to execute arbitrary commands through the pm2run function in the /rpc endpoint. The vulnerability has a CVSS score of 6.9 with publicly available exploit code, though the vendor has not yet responded to early notification of the issue. This represents a moderate-to-high risk for exposed elecV2P instances due to the combination of remote exploitability, low attack complexity, and confirmed public exploit availability.

Technical ContextAI

The vulnerability exists in elecV2P, a Node.js-based runtime environment tool, specifically within the pm2run function of the /rpc (remote procedure call) endpoint. The flaw is classified as CWE-78 (Improper Neutralization of Special Elements used in an OS Command, aka OS Command Injection), indicating that user-supplied input is passed unsanitized to OS command execution functions. The /rpc endpoint likely uses pm2 (a popular Node.js process manager) for command execution, and the pm2run function fails to properly validate or escape parameters before passing them to shell or exec operations. This allows attackers to inject arbitrary shell metacharacters and commands that are executed with the privileges of the elecV2P process.

RemediationAI

Immediate action required: upgrade elecV2P to a version released after 3.8.3 that contains a fix for the pm2run command injection vulnerability. As the vendor has not yet responded according to the disclosure timeline, check the official GitHub repository (https://github.com/elecV2/elecV2P/) for patched releases or security advisories. If a patched version is not yet available, restrict network access to the /rpc endpoint using a firewall or reverse proxy until an update is released, or disable the pm2run function if it is not essential to your deployment. Monitor the VulDB advisory (https://vuldb.com/vuln/353897) and the project's GitHub issues for vendor response and patch availability announcements.