Skip to main content
MediumCodeOWASP A03:2021CWE-94

How to fix: eval() Usage in Inline Scripts

Direct eval() calls found in inline scripts.

Why it matters

eval() can execute arbitrary code if input is attacker-controlled.

eval() interprets strings as code, creating injection risks.

How to fix it

  1. 1Replace eval() with JSON.parse() or safe alternatives.

Code examples

Replace eval() with safe alternatives

JavaScript
// BAD
eval(userInput);

// GOOD: use JSON.parse for data
const data = JSON.parse(input);

// GOOD: use a function map instead of eval for dynamic dispatch
const ops = { add: (a, b) => a + b, sub: (a, b) => a - b };
const fn = ops[userOp];
if (!fn) throw new Error("Unknown op");
const result = fn(a, b);

References

Detected automatically by VulnRadar. The check id is eval-in-scripts, stable across every scan so you can filter or diff on it.

See every code check

Questions

How severe is eval() Usage in Inline Scripts?
VulnRadar rates this medium 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-in-scripts, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does eval() Usage in Inline Scripts 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.

Propose a checkHow a check is built

Scan your own site for eval() usage in inline scripts

VulnRadar runs this check and hundreds more against a URL in seconds. No agent to install, just paste a URL.

Or scan this site as a demoRead the docs

How to fix: eval() Usage in Inline Scripts | VulnRadar