sast-ssti

Trace dynamic template strings to detect SSTI vulnerabilities across multi-language codebases.

1.3k|61|Updated Mar 30, 2026
One-click install
npx skills add https://github.com/utkusen/sast-skills --skill sast-ssti
Or copy as Structured Prompt for Agent▼
Please help me install this Agent Skill.
Skill: sast-ssti
Source: https://github.com/utkusen/sast-skills/tree/main/sast-files/.agents/skills/sast-ssti
Command: npx skills add https://github.com/utkusen/sast-skills --skill sast-ssti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SSTI (Server-Side Template Injection) vulnerabilities allow attackers to execute code by injecting dynamic template strings into rendering engines. This Skill provides a structured, three-phase workflow to locate, verify, and consolidate SSTI findings across a codebase to prevent remote code execution and data leakage.

Core Features & Use Cases

  • Three-phase SSTI assessment: recon to identify dynamic template rendering sites, batched verify to taint-track user input into templates, and merge to produce a consolidated report.
  • Architecture-guided scanning: leverages sast/architecture.md to tailor checks to the project's tech stack and rendering patterns.
  • Actionable remediation guidance: outputs include clear risk classifications and remediation recommendations in sast/ssti-results.md.

Quick Start

Run the SSTI workflow against your repository to identify dynamic template rendering sites and triage potential SSTI risks.

Frequently Asked Questions about sast-ssti

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I detect server-side template injection vulnerabilities in a codebase?▼

Detect server-side template injection vulnerabilities by tracing dynamic template strings across a codebase to locate where user input reaches rendering calls. This process applies taint-tracking across multiple languages to identify potential remote code execution risks.

Does SSTI scanning work with multiple web frameworks like Jinja2 and Twig?▼

SSTI scanning works with multiple web frameworks including Python/Jinja2, Node/Nunjucks, Java/FreeMarker, and PHP Twig. It traces user input into rendering calls across these multi-language stacks to locate dynamic template rendering sites.

What is the best way to trace user input reaching template rendering calls?▼

The best way to trace user input reaching template rendering calls is through a three-phase assessment: recon to identify rendering sites, batched verification to taint-track input, and a final merge to produce a consolidated report with actionable remediation guidance.

How do I remediate template injection risks after identifying rendering sites?▼

Remediate template injection risks using the phased artifacts generated during scanning, including sast/ssti-results.md. This final consolidated report provides clear risk classifications and specific recommendations to fix the dynamic template rendering vulnerabilities.

Can I tailor vulnerability checks to my project's specific tech stack and rendering patterns?▼

You can tailor vulnerability checks to your project's specific tech stack and rendering patterns using architecture-guided scanning. It leverages sast/architecture.md to adapt the analysis to the particular frameworks and rendering engines used in your codebase.