ssti-hunter

Detect, fingerprint, and exploit Server-Side Template Injection vulnerabilities in web applications.

30|6|Updated May 13, 2026
One-click install
npx skills add https://github.com/Rifteo/skills --skill ssti-hunter
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: ssti-hunter
Source: https://github.com/Rifteo/skills/tree/main/ssti-hunter
Command: npx skills add https://github.com/Rifteo/skills --skill ssti-hunter

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires requests, bs4, pynacl, requests-fuzz, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

The ssti-hunter Skill automates the detection and exploitation of Server-Side Template Injection (SSTI) vulnerabilities, ensuring thorough identification and handling of such security risks.

Core Features & Use Cases

  • SSTI Detection: Identifies vulnerable points in a server-side application.
  • Engine Fingerprinting: Determines the template engine used in SSTI.
  • Exploitation: Provides methods for exploiting SSTI to achieve Remote Code Execution (RCE).
  • Use Case: Use this Skill in security audits or penetration testing to quickly find and exploit SSTI vulnerabilities in web applications.

Quick Start

Run the 'ssti-hunter' Skill on the target application to automatically detect SSTI vulnerabilities.

Frequently Asked Questions about ssti-hunter

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

FAQPage Schema
How do I detect Server-Side Template Injection vulnerabilities during a web application audit?

To detect Server-Side Template Injection vulnerabilities, you can automate systematic detection and payload testing across web application inputs. This identifies vulnerable server-side template rendering points and verifies if injection is possible.

What is the best way to identify the template engine used in an SSTI attack?

The best way to identify the template engine used in an SSTI attack is through engine fingerprinting. This process systematically tests payloads to determine the specific engine, such as Jinja2, Twig, or Smarty, handling the server-side rendering.

Do I need Python libraries to exploit SSTI vulnerabilities and achieve Remote Code Execution?

Yes, exploiting SSTI vulnerabilities to achieve Remote Code Execution requires Python libraries such as requests, bs4, pynacl, and requests-fuzz. These dependencies facilitate the systematic analysis and payload testing needed for successful exploitation.

Can I get RCE payloads for Jinja2 and Twig template engines?

Yes, you can obtain RCE payloads specifically for Jinja2, Twig, Smarty, and other template engines. The exploitation process provides tailored methods and payloads designed for the identified engine to successfully achieve Remote Code Execution.

Does SSTI exploitation work on all web applications using template engines?

SSTI exploitation targets web applications with vulnerable server-side template rendering. It focuses on identifying and exploiting injection points in supported engines like Jinja2 and Twig, rather than universally affecting all web applications.