sc-ssti

Detects and verifies server-side template injection vulnerabilities across major template engines.

56|5|Updated Apr 8, 2026
One-click install
npx skills add https://github.com/ersinkoc/security-check --skill sc-ssti
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: sc-ssti
Source: https://github.com/ersinkoc/security-check/tree/main/skills/sc-ssti
Command: npx skills add https://github.com/ersinkoc/security-check --skill sc-ssti

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

Server-Side Template Injection (SSTI) vulnerabilities occur when user input becomes part of template code, enabling attackers to execute code or access sensitive data. This Skill helps identify and verify such vulnerabilities across multiple template engines to reduce risk in web applications.

Core Features & Use Cases

  • Cross-engine SSTI detection across Python (Jinja2), PHP (Twig/Freemarker), Java (Velocity/Thymeleaf), Ruby (ERB), Go templates, and Node templates.
  • Phase-based discovery and verification to differentiate safe data usage from unsafe template code and to provide concrete remediation guidance.
  • Use Case: Scan a codebase containing templates and rendering logic to surface instances where user input is interpolated into template strings.

Quick Start

Scan your project for SSTI vulnerabilities across supported template engines with the detector.

Frequently Asked Questions about sc-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 my codebase?

Server-side template injection detection involves scanning codebases to find where untrusted user input is interpolated into template strings. The tool distinguishes safe data usage from unsafe template code execution across multiple engines using discovery and verification phases.

What template engines are vulnerable to SSTI and supported for scanning?

Vulnerable template engines covered include Python Jinja2, PHP Twig, Freemarker, Velocity, Ruby ERB, Thymeleaf, and Go templates. Engine-specific patterns are applied during discovery and verification to accurately identify server-side template injection risks.

How do I scan a web application for SSTI across different template engines?

To scan for SSTI, run the detector against your project codebase containing templates and rendering logic. It applies engine-specific patterns across supported languages to surface instances where user input becomes part of template code execution.

Does this SSTI scanner support Java Thymeleaf and Velocity templates?

Yes, this SSTI scanner supports Java Thymeleaf and Velocity templates. It also covers Python Jinja2, PHP Twig, Freemarker, Ruby ERB, and Go templates, applying engine-specific patterns to verify injection vulnerabilities.

What is the difference between safe data usage and server-side template injection?

Safe data usage passes user input as variables to templates, while server-side template injection occurs when user input becomes part of template code. The verification phase differentiates the two to produce actionable findings and remediation guidance.

What remediation guidance is provided after finding SSTI vulnerabilities?

Remediation guidance provides actionable steps to fix server-side template injection vulnerabilities found during verification. It focuses on securing template rendering logic across supported engines like Jinja2, Twig, and Thymeleaf.