Skip to main content
HighCodeOWASP A03:2021CWE-78

How to fix: Potential Command Injection Vectors

Code patterns that execute system commands, potentially vulnerable to command injection.

Why it matters

Command injection allows attackers to execute arbitrary system commands.

Executing system commands with user-controlled input is extremely dangerous.

How to fix it

  1. 1Never pass user input to system command functions.
  2. 2Use language-native APIs instead of shell commands.
  3. 3Run with minimal privileges.

Code examples

Safe alternative

TypeScript
// BAD: exec(`rm ${userFile}`);
// GOOD:
import { unlink } from 'fs/promises';
await unlink(sanitizedPath);

References

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

See every code check

Questions

How severe is Potential Command Injection Vectors?
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 command-injection, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Potential Command Injection Vectors map to?
It maps to CWE-78. 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 potential command injection vectors

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: Potential Command Injection Vectors | VulnRadar