VulnerabilityPublished 11 Mar 2026

CVE-2026-3955: elecV2P · Code Injection

Affects elecV2PSource CVE Database V5

Compare

Public exploit available · CVSS 5.3 Medium.

Data as of 30 Oct 2026, 11:52 UTC

CVSS 4.0 base score

5.3Medium

How severe the flaw is on the 0–10 CVSS scale.

EPSS: 0.2% chance of exploitation in 30 days – higher than 15% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.

CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:L/VI:L/VA:L/SC:N/SI:N/SA:N/E:P

Base metrics

Attack Vector: Network
Attack Complexity: Low
Attack Requirements: None
Privileges Required: Low
User Interaction: None
Vulnerable system confidentiality: Low
Vulnerable system integrity: Low
Vulnerable system availability: Low
Subsequent system confidentiality: None
Subsequent system integrity: None
Subsequent system availability: None

Threat metrics

Exploit Maturity: POC

Bold values are the worst case: easiest to exploit or largest impact.

Attack Vector: Network: The vulnerable system is bound to the network stack and the set of possible attackers extends beyond the other options listed below, up to and including the entire Internet. Such a vulnerability is often termed “remotely exploitable” and can be thought of as an attack being exploitable at the protocol level one or more network hops away (e.g., across one or more routers).
Attack Complexity: Low: The attacker must take no measurable action to exploit the vulnerability. The attack requires no target-specific circumvention to exploit the vulnerability. An attacker can expect repeatable success against the vulnerable system.
Attack Requirements: None: The successful attack does not depend on the deployment and execution conditions of the vulnerable system. The attacker can expect to be able to reach the vulnerability and execute the exploit under all or most instances of the vulnerability.
Privileges Required: Low: The attacker requires privileges that provide basic capabilities that are typically limited to settings and resources owned by a single low-privileged user. Alternatively, an attacker with Low privileges has the ability to access only non-sensitive resources.
User Interaction: None: The vulnerable system can be exploited without interaction from any human user, other than the attacker.
Vulnerable system confidentiality: Low: There is some loss of confidentiality. Access to some restricted information is obtained, but the attacker does not have control over what information is obtained, or the amount or kind of loss is limited. The information disclosure does not cause a direct, serious loss to the Vulnerable System.
Vulnerable system integrity: Low: Modification of data is possible, but the attacker does not have control over the consequence of a modification, or the amount of modification is limited. The data modification does not have a direct, serious impact to the Vulnerable System.
Vulnerable system availability: Low: Performance is reduced or there are interruptions in resource availability. Even if repeated exploitation of the vulnerability is possible, the attacker does not have the ability to completely deny service to legitimate users. The resources in the Vulnerable System are either partially available all of the time, or fully available only some of the time, but overall there is no direct, serious consequence to the Vulnerable System.
Subsequent system confidentiality: None: There is no loss of confidentiality within the Subsequent System or all confidentiality impact is constrained to the Vulnerable System.
Subsequent system integrity: None: There is no loss of integrity within the Subsequent System or all integrity impact is constrained to the Vulnerable System.
Subsequent system availability: None: There is no impact to availability within the Subsequent System or all availability impact is constrained to the Vulnerable System.
Exploit Maturity: POC: Based on threat intelligence sources each of the following must apply: · Proof-of-concept is publicly available · No knowledge of reported attempts to exploit this vulnerability · No knowledge of publicly available solutions used to simplify attempts to exploit the vulnerability

Definitions: FIRST CVSS v4.0 specification.

Exploitation evidence

Disclosed: evidence found.
CVE published 11 Mar 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: evidence found.
CVSS exploit maturity: proof of concept public
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), CVSS vector, the Metasploit, Exploit-DB and nuclei-templates index as of 30 Oct 2026.

Disclosed: The CVE record is public on cve.org. Its publication is t = 0.
Detectable: A public nuclei template can find exposed instances, for defenders and attackers alike.
Weaponized: A Metasploit exploit module or Exploit-DB entry exists (Metasploit scanner modules do not count), or CISA SSVC or the CVSS exploit maturity reports a public proof of concept.
Exploited in the wild: CISA KEV lists it, CISA SSVC rates exploitation active, or a source reports attacks.
Observed by OffSeq Mirage: OffSeq Mirage honeypot sensors recorded attack traffic for this CVE, or found exposed hosts without attack traffic.

Moments are spaced evenly, not to scale; a dashed line marks a gap of six months or more. Deltas count from t = 0. Sources that give only a date (CISA KEV, Exploit-DB, or a time of exactly 00:00Z) read “same day” rather than hours. Metasploit modules carry the flaw’s disclosure date, not their release date, and nuclei templates carry no date, so both appear above but not on the timeline.

What to do

Affected software

Product	Affected	Fixed in
elecV2P	Affected 3.8.0 – 3.8.3 4 affected builds	Fixed in–
GitHubelecv2/elecV2P`pkg:github/elecv2/elecV2P`Other threats	Affected 3.8.0 – 3.8.3 4 affected builds	Fixed in–

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

To mitigate CVE-2026-3955, organizations should first assess their deployment of elecV2P and identify any instances running affected versions (3.8.0 to 3.8.3). Until an official patch is released, consider the following specific actions: 1) Restrict network access to the elecV2P service, limiting exposure to trusted internal networks only. 2) Implement strict input validation and sanitization at the application or proxy level to block malicious JavaScript payloads targeting the runJSFile function. 3) Employ runtime application self-protection (RASP) or web application firewalls (WAFs) configured to detect and block code injection attempts. 4) Monitor logs and network traffic for unusual activity related to the jsfile endpoint, including unexpected script execution or anomalous requests. 5) If feasible, isolate elecV2P instances in segmented network zones to contain potential compromise. 6) Engage with the elecV2P development community to track patch releases and apply updates promptly once available. 7) Consider alternative tools or versions not affected by this vulnerability if immediate risk reduction is necessary. These targeted mitigations go beyond generic advice by focusing on network segmentation, input filtering, and active monitoring specific to the vulnerability's characteristics.

Description

CVE-2026-3955 is a medium-severity code injection vulnerability affecting elecV2P versions up to 3.8.3. The flaw exists in the runJSFile function within the jsfile endpoint, allowing remote attackers to inject and execute arbitrary code without authentication or user interaction. Although the vulnerability has a CVSS score of 5.3, exploitation requires low privileges but no user interaction, and impacts confidentiality, integrity, and availability to a limited extent. The vulnerability was responsibly disclosed but remains unpatched as of the publication date. No known exploits are currently observed in the wild. Organizations using elecV2P should prioritize mitigating this risk due to the potential for remote code execution. Countries with significant elecV2P usage and strategic interest in automation or IoT deployments are most at risk.

Impact

The primary impact of CVE-2026-3955 is the potential for remote code execution on systems running vulnerable versions of elecV2P. Successful exploitation could allow attackers to execute arbitrary JavaScript code, potentially leading to unauthorized access, data manipulation, or disruption of service. Given the nature of elecV2P as an automation and scripting platform, attackers might leverage this vulnerability to pivot within internal networks, manipulate IoT devices, or disrupt automated workflows. While the CVSS score indicates a medium severity, the lack of required user interaction and the remote attack vector increase the risk profile. Organizations relying on elecV2P for critical infrastructure automation or IoT management could face operational disruptions, data breaches, or loss of control over connected devices. The absence of a patch and public exploit disclosure further elevate the urgency for mitigation. However, the requirement for low privileges to exploit somewhat limits the attack surface to environments where attackers already have some level of access.

Summary

CVE-2026-3955 is a code injection vulnerability identified in the elecV2P project, specifically affecting versions 3.8.0 through 3.8.3. The vulnerability resides in the runJSFile function located in the source-code/elecV2P-master/webser/wbjs.js file, which is part of the jsfile endpoint component. This function improperly handles input, allowing an attacker to inject malicious JavaScript code remotely. The attack vector is network-based (AV:N), requiring low attack complexity (AC:L) and no authentication (PR:L) or user interaction (UI:N). The vulnerability impacts confidentiality, integrity, and availability at a low level (VC:L, VI:L, VA:L), indicating that while exploitation can lead to unauthorized code execution, the scope and impact are somewhat limited. The public disclosure and availability of exploit information increase the risk of exploitation, although no active exploitation has been reported. The vulnerability affects the core functionality of elecV2P, a tool often used for automation and scripting in IoT and smart home environments, making it a significant concern for users relying on this software for critical operations.

References

Community reviews

Loading reviews…

Exploitation evidence

What to do

Affected software

Description

AI analysisMachine-generated, updated 19 Mar 2026, 02:30 UTC

Technical details

References

Community reviews

Related threats