hunt-ssti

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

Updated Jul 1, 2026
One-click install
npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill hunt-ssti-bpnrockstar
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: hunt-ssti
Source: https://github.com/bpnrockstar/UnifiedBugHunter/tree/main/skills/hunt-ssti
Command: npx skills add https://github.com/bpnrockstar/UnifiedBugHunter --skill hunt-ssti-bpnrockstar

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

This Skill identifies and leverages server-side template injection (SSTI) vulnerabilities, which can lead to remote code execution (RCE).

Core Features & Use Cases

  • SSTI Detection: Identifies SSTI across various template engines like Jinja2, Twig, Freemarker, ERB, and more.
  • RCE Escalation: Escalates from SSTI to RCE using engine-specific patterns.
  • Target Testing: Tests email templates, PDF generators, CMS features, and error pages for SSTI.
  • Use Case: When performing security testing on a web application, this Skill can be used to detect and exploit SSTI vulnerabilities.

Quick Start

Use the hunt-ssti skill to test for SSTI in the 'user-profile' endpoint of the target application.

Frequently Asked Questions about hunt-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 web applications?

Server-side template injection vulnerabilities are detected by injecting template syntax probes into target endpoints and analyzing application responses for template engine execution. This Skill automates detection across various template engines by testing user-specified endpoints.

Can I escalate server-side template injection to remote code execution across different template engines?

Yes, server-side template injection can be escalated to remote code execution using engine-specific patterns. This Skill applies tailored exploitation payloads for template engines like Jinja2, Twig, Freemarker, and ERB to achieve RCE during security testing.

What web application features should I test for SSTI vulnerabilities?

Email templates, PDF generators, CMS features, and error pages are common targets for SSTI vulnerabilities. You should test these components by specifying the relevant target endpoint and template engine to identify injection points during security assessments.

Does this SSTI detection method support template engines like Jinja2, Twig, Freemarker, and ERB?

Yes, this SSTI detection supports template engines including Jinja2, Twig, Freemarker, and ERB. It applies engine-specific patterns to both identify injection vulnerabilities and escalate them to remote code execution across these frameworks.

How do I start testing a specific endpoint for template injection?

To start testing for template injection, manually specify the target endpoint and the template engine used by the application. The Skill then probes the endpoint with template syntax to detect vulnerabilities and attempts RCE escalation.

Why does finding SSTI require specifying the template engine manually?

Specifying the template engine manually is required because SSTI exploitation relies on engine-specific syntax and patterns to escalate to remote code execution. Accurate engine identification ensures the correct payloads are used during vulnerability detection.