How to fix: eval() Code Injection Risk
JavaScript eval() function calls detected.
Why it matters
eval executes arbitrary code, enabling code injection.
eval() is one of the most dangerous JavaScript functions.
How to fix it
- 1Replace eval with JSON.parse or safer alternatives.
Code examples
Replace eval with a safe function map
// Instead of: eval(userOp + "(data)")
// Build an explicit dispatch table:
const handlers = {
process: processData,
validate: validateData,
transform: transformData,
};
const fn = handlers[userOp];
if (typeof fn !== "function") throw new Error("Unknown operation");
fn(data);References
Detected automatically by VulnRadar. The check id is eval-usage, stable across every scan so you can filter or diff on it.
More code checks
- CriticalForm Submits Data Over Insecure HTTP
- MediumPotential Prototype Pollution Sinks Detected
- HighPotential Command Injection Vectors
- HighJWT Decoded Without Signature Verification
- HighPotential Path Traversal Vulnerability
- HighInsecure Authentication Mechanisms Detected
- HighPotential Insecure Deserialization
- Mediumeval() Usage in Inline Scripts
Questions
- How severe is eval() Code Injection Risk?
- VulnRadar rates this high severity in the code category. The severity is fixed per check, not scored per site, so the same finding is the same severity on every scan.
- Does VulnRadar check for this automatically?
- Yes. It runs as part of every scan under the check id eval-usage, which stays the same between runs so you can filter, diff, or gate CI on it.
- Which standards does eval() Code Injection Risk map to?
- It maps to CWE-94. In the OWASP Top 10 it falls under A03:2021.
Missing a check?
The detection set is open. If you know a misconfiguration this does not catch, propose it: the issue template asks for the threat model, how to detect it, the false-positive risk, and a test fixture, which is the same thing a maintainer would have to work out anyway.