← All finding types

ssti_vulnerability

CWE-1336

Ssti Vulnerability — a PullGuard finding type. Findings of this type appear in the PR comment, Step Summary, SARIF (GitHub Security tab / IDE viewers), and the HTML report, each with severity, location, and the remediation guidance below.

How to fix

Compile templates from literal strings only — pass user data as context medium effort

// Jinja2 (WRONG)
render_template_string(user_input)

// Jinja2 (RIGHT)
render_template("page.html", username=user_input)

// Handlebars (WRONG)
const tpl = Handlebars.compile(userProvidedSource);

// Handlebars (RIGHT)
const tpl = Handlebars.compile(LITERAL_SOURCE);
tpl({ name: user_input });

Triage

Suppress a confirmed non-issue with a committed .pullguardignore entry (pullguard ignore locally, or comment /pullguard ignore <fingerprint> <reason> on the PR — the fingerprint is printed in the PR comment’s Triage section). Entries support expiresAt for time-boxed snoozes.

Security findings at major or critical severity — and any critical finding — always surface: .pullguardignore cannot hide them. The reviewed paths that keep them visible are acknowledged (reviewed, stays in reports) and, for a confirmed false positive, a reasoned false_positive entry — visible and audited, excluded only from the merge block.