Authenticated code execution via raw jscontent evaluation
Published Mar 11, 2026 · Updated Mar 11, 2026
Code injection in the jsfile endpoint in elecV2P 3.8.0 through 3.8.3 allows remote authenticated users to execute JavaScript code. The endpoint passes the user-supplied jscontent value to runJSFile as raw code when type is set to totest, allowing Node.js APIs to launch system commands. Low-privileged access to the web interface is required; successful exploitation runs commands with the service process's operating-system privileges.
Summary
What happened
Code injection in the jsfile endpoint in elecV2P 3.8.0 through 3.8.3 allows remote authenticated users to execute JavaScript code. The endpoint passes the user-supplied jscontent value to runJSFile as raw code when type is set to totest, allowing Node.js APIs to launch system commands. Low-privileged access to the web interface is required; successful exploitation runs commands with the service process's operating-system privileges.
The record
- CVE
- CVE-2026-3955
- Published
- Mar 11, 2026
- Updated
- Mar 11, 2026
- Vendor
- elecV2
- Product
- elecV2P
- Classifications
- CWE-74, CWE-94, T1059.007
- Attack vector
- network
- Privileges
- authenticated
Timeline
How it unfolded
- Mar 11, 2026CVE publishedPublication date reported by the CVE source.
- Mar 11, 2026Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=3.8.0
- Affected versionversion=3.8.1
- Affected versionversion=3.8.2
- Affected versionversion=3.8.3
What conditions does exploitation require?
What is affected?
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
- GitHub issue 194 proof of conceptproof of concept · demonstrated
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo