ssti-poc

Detect and exploit server-side template injection vulnerabilities to achieve remote code execution.

5|3|Updated Apr 10, 2026
One-click install
npx skills add https://github.com/zebbern/termstack --skill ssti-poc
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssti-poc
Source: https://github.com/zebbern/termstack/tree/main/.github/skills/ssti-poc
Command: npx skills add https://github.com/zebbern/termstack --skill ssti-poc

SYSTEM DOCUMENTATION & REQUIREMENTS

What problem does it solve?

SSTI-POC helps security researchers identify and validate server-side template injection vulnerabilities to confirm remote code execution paths in real-world templates.

Core Features & Use Cases

  • Detection & Exploitation: Uses SSTImap-based workflows to detect SSTI and attempt exploit payloads across multiple template engines.
  • Support for Legacy Tools: Includes tplmap references for historical templates and TInjA for efficient SSTI/CSTI scanning.
  • Guided Scenarios: Provides concrete lab-use cases for validation, assessment, and documentation of SSTI risks.

Quick Start

Run SSTI-POC in a secure lab against a test URL to validate SSTI vulnerabilities and demonstrate possible RCE.

Frequently Asked Questions about ssti-poc

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

FAQPage Schema
How do I detect and exploit server-side template injection vulnerabilities?

Server-side template injection vulnerabilities are detected and exploited by injecting payloads into user-supplied templates rendered by engines like Jinja2, Twig, or Freemarker. This Skill provides an end-to-end workflow covering detection, interactive exploration, payload delivery, and remote code execution validation.

Can I use this to verify remote code execution across multiple template engines?

Yes, remote code execution can be verified across multiple template engines including Jinja2, Twig, Freemarker, ERB, Nunjucks, Velocity, Pug, and Smarty. It applies SSTImap-based workflows to deliver exploit payloads and achieve OS-shell or file-read capabilities for validation.

What is the best way to scan for SSTI vulnerabilities in web applications?

The best way to scan for SSTI vulnerabilities is using guided scenarios that reference tools like SSTImap, tplmap, and TInjA. These tools enable efficient detection, interactive exploration, and exploitation workflows to validate template injection risks in web applications.

Does this workflow support both modern and legacy template injection scanning?

Yes, modern and legacy template injection scanning are supported. It references SSTImap and TInjA for efficient current SSTI detection, while including tplmap references for validating historical templates to ensure comprehensive coverage across different template engines.

How do I validate SSTI risks safely in a test environment?

SSTI risks are validated safely by running detection and exploitation workflows in a secure lab against a test URL. This approach allows you to verify remote code execution paths, demonstrate possible exploits, and document template injection risks without impacting production systems.

Why does server-side template injection lead to remote code execution?

Server-side template injection leads to remote code execution when web applications render user-supplied templates using engines like Jinja2 or Smarty. Attackers can inject malicious payloads that the engine executes, enabling OS-shell access or file-read capabilities through the template rendering process.