CVE-2026-5011
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 vulnerability was detected in elecV2 elecV2P up to 3.8.3. This vulnerability affects the function runJSFile of the file /webhook of the component JSON Parser. Performing a manipulation of the argument rawcode results in code injection. Remote exploitation of the attack is possible. The exploit is now public 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 · moderate confidenceCode injection vulnerability in elecV2P through the /webhook endpoint's runJSFile function. User-supplied input to the 'rawcode' argument is executed without proper sanitization, allowing arbitrary JavaScript code execution.
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
- Low
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.1/AV:N/AC:L/PR:L/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 if elecV2P is installedSearch for elecV2P installation directories, check for process named 'elecv2p', or look for its characteristic files (such as config.json, script folders)Affected if elecV2P software is present on the system
-
Determine installed versionCheck the package.json, version file, or the application's startup logs for the elecV2P version number; compare against any known version releasesAffected if The installed version falls within any affected version range (if known) or is an unpatched version
-
Verify /webhook endpoint is accessibleCheck network configuration, firewall rules, or reverse proxy settings to confirm the /webhook endpoint is exposed and reachable from the networkAffected if The /webhook endpoint is externally accessible or accessible beyond intended trusted boundaries
-
Inspect runJSFile function configurationReview the elecV2P configuration files or source code for the runJSFile function definition; check if it processes the 'rawcode' parameterAffected if The runJSFile function accepts rawcode input without documented sanitization logic
-
Review access controls on /webhookExamine authentication, authorization, or IP restriction settings applied to the /webhook endpoint in config files or the application's access control settingsAffected if No authentication, authorization, or IP whitelisting is required to access the /webhook endpoint
A user is affected if elecV2P is running with the /webhook endpoint accessible and the runJSFile function processing unsanitized rawcode input without access restrictions.
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 dataImplement strict input validation on the rawcode parameter before passing to runJSFile; consider whitelisting allowed characters/patterns. Until a patch is released, restrict access to the /webhook endpoint or disable the functionality if not required.
- Consultation2.0 h
- Implementation4.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,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-5011 — 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-5011 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