CVE-2026-5012
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedA 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.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceOS command injection vulnerability in the pm2run function within the /rpc endpoint of elecV2P up to version 3.8.3 allows remote attackers to execute arbitrary operating system commands via specially crafted input.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify elecV2P installation and versionCheck for elecV2P installation directory or running process. Look for version file or check the UI/about page for the installed version number. Compare against the affected range: versions 3.8.3 and below are affected.Affected if elecV2P version 3.8.3 or any earlier version is installed
-
Verify the /rpc endpoint is network-accessibleCheck network configuration, firewall rules, or reverse proxy settings to determine if the /rpc endpoint is exposed to untrusted networks or the internet. Test with: curl http://TARGET/rpcAffected if The /rpc endpoint is reachable from untrusted networks or the internet
-
Confirm pm2run function is accessibleAttempt to invoke the pm2run function through the /rpc endpoint with a test request (e.g., sending a JSON request to /rpc with the pm2run method). Inspect the application logs for successful execution.Affected if The pm2run function responds to requests and can be invoked through the /rpc endpoint
-
Review access logs for suspicious /rpc requestsExamine web server access logs, application logs, or any /rpc endpoint request logs for unusual or unexpected commands, especially those containing shell metacharacters (;, |, &, $(...), backticks, etc.)Affected if Logs show requests to /rpc containing shell command syntax or unexpected command patterns
You are affected if elecV2P version 3.8.3 or earlier is installed AND the /rpc endpoint is network-accessible with the pm2run function enabled and callable.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
From vendor dataRestrict network exposure of the /rpc endpoint, implement strict input validation and sanitization on the pm2run function to prevent command injection, and upgrade to a patched version once available.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5012 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-5012 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data