Skip to main content
HighCodeOWASP A03:2021CWE-94

How to fix: Function Constructor Usage

new Function() usage detected.

Why it matters

Similar to eval(), can execute arbitrary code.

Function constructor creates functions from strings.

How to fix it

  1. 1Avoid Function constructor, use direct function definitions.

Code examples

Avoid new Function() with user input

JavaScript
// BAD: equivalent to eval()
const fn = new Function("x", userInput);

// GOOD: define functions statically
const validators = {
  email: (x) => /^[^@]+@[^@]+$/.test(x),
  number: (x) => !isNaN(Number(x)),
};
const validate = validators[userType];
if (!validate) throw new Error("Unknown type");
validate(input);

References

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

See every code check

Questions

How severe is Function Constructor Usage?
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 function-constructor, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Function Constructor Usage 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 function constructor usage

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: Function Constructor Usage | VulnRadar