Skip to main content
HighCodeOWASP A03:2021CWE-1336

How to fix: Template Injection Indicators

Template syntax detected in output.

Why it matters

Server-Side Template Injection can lead to RCE.

Unescaped template expressions can execute arbitrary code.

How to fix it

  1. 1Escape all user input before template rendering.

Code examples

Never pass user input directly to template engines

TypeScript
// BAD: user controls the template string
const result = template.render(userInput, context);

// GOOD: user input goes into the data, not the template
const tmpl = "Hello {{ name }}!";
const result = template.render(tmpl, { name: userInput }); // name is escaped

// For Nunjucks, Handlebars, etc.: always escape output by default

References

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

See every code check

Questions

How severe is Template Injection Indicators?
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 ssti-indicators, which stays the same between runs so you can filter, diff, or gate CI on it.
Which standards does Template Injection Indicators map to?
It maps to CWE-1336. 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 template injection indicators

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: Template Injection Indicators | VulnRadar