PAGES
← all tools
◆ Web Application Security

sstimap

v1.4 open-source

Automatic SSTI detection tool with interactive interface

Summary

sstimap is an open-source command-line tool, released under GPL-3.0, that scans websites for Server-Side Template Injection and code injection vulnerabilities and exploits them to gain access to the underlying operating system. It is built for penetration testers running interactive engagements rather than automated baseline scanning, offering an interactive mode and a shell for executing commands once a flaw is confirmed. It is based on Tplmap's code but the README describes it as diverging from that project, adding new detection techniques, broader template-engine coverage across Java, JavaScript, PHP, Python and Ruby, and blind-injection handling with MD5-based file confirmation. Development is small, with two contributors since 2022, but active: seven tracked releases and a commit as recently as 39 days ago.

Automatic SSTI detection tool with interactive interface

How sstimap helps

Can I turn this injection into a shell on the box?

once a vulnerable point is confirmed, drops into an interactive session that lets you run a single OS command or open a full shell through the same injection point

Is this SSTI exploitable when there's no direct output to read from?

falls back to boolean and error-based blind techniques, and can confirm exploitation through file-upload checks like MD5 and existence tests when no response is ever reflected

Which template or scripting engine is actually rendering this input?

runs engine-specific plugins (covering engines like Spring EL, Freemarker, Twig, Mustache, Pybars and Dust.js, plus generic eval-style languages) and reports which plugin's payloads succeeded, identifying the engine behind the injection

Do I need to re-find the same vulnerabilities in tomorrow's retest?

can save confirmed vulnerabilities to a file during one session and reload them in a later run instead of re-scanning from scratch

Can I test an endpoint that sits behind a login?

crawling and form detection carry the headers and cookies you supply, so authenticated pages get scanned the same way as open ones

all 12 features, with the evidence for each →

Languages

Not documented

Features

12 capabilities · 2 backed by code, an API document or a real run

Built from sstimap's releases, docs, README and our own runs. “Seen” marks the month we first spotted a release the vendor didn't date. Group names and tags are our labels.

Compare with peers →

  • sstimap covers 1 of the 8 vulnerability assessment methods capabilities we track.

What sstimap offers you

  • Command-line interface2
  • Plugin API support1
  • Plugin system1
Web vulnerability scanning 4 features Vulnerability assessment methods since 2023
SSTI plugin ecosystem shipped Provides a plugin architecture for detecting and exploiting SSTI vulnerabilities in various template engines. 7 releases · first seen Aug 2025

Shared capability: Web vulnerability scanning

Also counts toward: Plugin API support, Plugin system

release 7 total

  • New plugin for fuzzing uncommon and legacy evaluating template injection patterns. v1.4 · Aug 2026 · source · release history
  • New plugin detects GHSA-5hrj-7fc3-cmx9 in Mustache template engine. v1.4 · Aug 2026 · source · release history
  • New plugin supports Pybars3 and Pybars4 template engines for detection and exploitation. v1.4 · Aug 2026 · source · release history
  • Adds new plugins for GHSA-5hrj-7fc3-cmx9 (Mustache), Pybars3, Pybars4, and fuzzing uncommon/legacy evaluating templates v1.4 · Aug 2026 · source · release history
  • New plugin for Spring EL injection detection and exploitation. v1.3 · Aug 2025 · source · release history
  • Dust.js now supports rendered code execution. v1.3 · Aug 2025 · source · release history
Injection point selection verified Allows the user to specify which HTTP request components (query string, body, headers, cookies) are tested for injection vulnerabilities. 5 releases · 1 other source · first seen Apr 2023

Shared capability: Web vulnerability scanning

release

  • Crawling and form detection now respect user-supplied headers and cookies, enabling authenticated crawl sessions. v1.4 · Aug 2026 · source · release history
  • Plugins can now specify header and trailer length for more precise injection control. v1.3 · Aug 2025 · source · release history
  • Context suffix can now include closure or reversed closure. v1.3 · Aug 2025 · source · release history
  • Adds --req-body-type flag (json, text, fromhex) to handle non-URLencoded request bodies v1.2 · Jan 2024 · source · release history
  • --engine cheetah selects the new Cheetah template engine for payload generation. v1.1 · Apr 2023 · source · release history

command line

  • --injection-points — Injection points to test without markers: Q(uery) B(ody) H(eaders) C(ookies). Default: QBHC v1.3.3 · Mar 2026 · command-line history
SSTI detection techniques shipped Offers various techniques for detecting SSTI, including error-based and boolean blind detection methods. 2 releases · first seen Aug 2025

Shared capability: Web vulnerability scanning

release

  • Adds error-based detection and exploitation technique for SSTI scanning. v1.3 · Aug 2025 · source · release history
  • Adds boolean error-based blind detection and exploitation technique. v1.3 · Aug 2025 · source · release history
Fallback SSTI detection shipped Allows running SSTI detection without form detection when optional dependencies are missing. 1 release · first seen Aug 2025

Shared capability: Web vulnerability scanning

release

  • SSTImap can now run with form detection disabled when optional dependencies are not installed. v1.3 · Aug 2025 · source · release history
Other / not yet classified 8 features Features we have not matched to a capability yet. A suggested match is marked.
Vulnerability session persistence verified Enables saving detected vulnerabilities to files and reloading them in later sessions. 2 releases · 2 other sources · first seen Aug 2026

release

  • Adds --save-vulns and --load-vulns flags to persist and reload detected vulnerabilities across sessions v1.4 · Aug 2026 · source · release history
  • Adds ability to save detected vulnerabilities to file and reload them in a later session. v1.4 · Aug 2026 · source · release history

command line

  • --save-vuln — File or directory to save detected vulnerability to v1.4 · Aug 2026 · command-line history
  • --load-vuln — File or directory to load vulnerability from (use '-' for STDIN) v1.4 · Aug 2026 · command-line history
Request body format handling shipped suggested Supports non-standard request body types, including JSON, hex, and file-based data injection. 2 releases · first seen Jan 2024

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

Also counts toward: Command-line interface

release

  • Supports fromfile data type to supply request body parts from files. v1.3 · Aug 2025 · source · release history
  • Adds --req-body-type flag (json, text, fromhex) to handle non-URLencoded request bodies v1.2 · Jan 2024 · source · release history
Shell interpreter configuration shipped Allows specifying the target system shell or forcing a specific shell interpreter for OS command execution. 1 release · 1 other source · first seen Jan 2024

Also counts toward: Command-line interface

release

  • Adds --shell argument to specify the expected target system shell v1.2 · Jan 2024 · source · release history

example

  • Force the tool to use a specific shell interpreter (e.g., cmd.exe) when targeting Windows systems. sstimap -u http://target/app --shell cmd.exe v1.2 · Jan 2024 · source
Crawling and form detection configuration shipped suggested Allows the user to pass custom headers and cookies to the target application during crawling and form detection phases. 1 release · first seen Aug 2026

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

release

  • Crawling and form detection now pass provided headers and cookies to the target application v1.4 · Aug 2026 · source · release history
Exfiltration methods shipped Supports data exfiltration using Base64 encoding within plugin contexts. 1 release · first seen Aug 2025

release

  • Adds Base64 exfiltration support (available for plugin use). v1.3 · Aug 2025 · source · release history
Ordered technique testing shipped Allows techniques to be tested in a user-specified order rather than default sequences. 1 release · first seen Aug 2025

release

  • Enables ordered technique testing — techniques are now tested in the user-specified order. v1.3 · Aug 2025 · source · release history
Interactive development mode shipped Enables an interactive REPL environment for live module reloading and updates without restarting the scan. 1 release · first seen Apr 2023

release

  • Enables interactive mode with module reloading via a new REPL command, allowing live updates without restarting the scan. v1.1 · Apr 2023 · source · release history
Template engine payload selection shipped suggested Allows the user to select specific template engines or custom template engines for payload generation. 1 release · first seen Apr 2023

Suggested capability: Web vulnerability scanning. This is our guess, not confirmed.

release

  • --engine cheetah selects the new Cheetah template engine for payload generation. v1.1 · Apr 2023 · source · release history

Lines in monospace are the tool's own words: help text parsed from its source, or an endpoint from its API document. Under release, a line is our summary of a dated release. Under docs, it is quoted from the tool's own documentation or website. Each links back to the source it came from.

Score card

  1. Shipping velocity releases a month, last 12 months
  2. Documentation quality release-notes rubric, 0–100
  3. Breaking-change discipline how rarely a release breaks users, and notice given
  4. Maintenance risk quiet time against its own cadence, maintainers
  5. Innovation & surface new capabilities, API and MCP surface
  6. Community health
  7. Contributor trend distinct committers, this year against last
  8. Maintainer concentration bus factor now against a year ago
  9. Issue backlog trend issues closed per issue opened, 12 months
  10. Responsiveness median time to a maintainer’s first reply

Nine scores for sstimap, each built from the releases, notes and API history this site tracks — and, on Researcher and Business, where it stands among every measured tool in its category and how that has moved.

Score cards are part of every paid plan.

See plans →

Each score is 0–100 on a published rubric, derived from data this site already shows. A dimension we cannot measure says so — it is never scored 0 and never enters a rank.

How this is scored
  • Shipping velocity — releases a month over the last 12 months, on a log scale where 16 a month scores 100. Needs 3 releases in the window.
  • Documentation quality — the release-notes rubric published on the analytics page, unchanged.
  • Breaking-change discipline — the share of releases carrying a breaking change (none scores 100, half or more scores 0). Only projects that label breaking changes are measured: a clean record cannot be told from an unlabelled one.
  • Maintenance risk — quiet time measured against the tool's own release cadence (quiet longer than 90 days and three typical gaps scores 0), plus the number of active maintainers and whether contributors are growing, where known. Higher is lower risk.
  • Innovation & surface — new capabilities in the feature ledger this year, API and MCP operations added, and the share of commits that are features: the mean of whichever we hold.
  • Community health (open-source tools only) — each is a direction, not a size: contributors this year against last, the bus factor now against a year ago, and issues closed per issue opened, where steady scores 50, doubled 100 and halved 0; plus the median time to a maintainer's first reply (an hour scores about 100, a month or more 0). A commercial card has no repository and carries none of the four.
  • Documented delivery (commercial tools) — when a vendor's documented new capabilities have slowed against its own baseline, that counts against the overall standing as heavily as two low dimensions. Steady delivery, or too little history to judge, leaves the standing alone; it is never a sixth score.
  • Open-source tools are scored on repository signals; commercial tools on their published changelog. Ranks compare tools within one category and one profile and need at least five measured peers; the overall standing needs three ranked dimensions. Best-in-breed or consolidator is a shape, not a quality, and is never scored.

Release-note detail over time

See how much detail sstimap puts in its release notes, quarter by quarter, and compare it with tracked tools in the same category. This history uses up to ten retained, reviewed notes per tool; sparse or blank older quarters may reflect that limit.

Checking release-note history…

Explore the full chart →

Releases

Show

4 entries

  1. August 20261
  2. August 20251
  3. January 20241
  4. April 20231
    Show

    4 entries

    Project health

    Issue, contributor and maintainer activity in vladko312/SSTImap, 2023-10 – 2026-09, as of 2026-09-25. Twelve-month figures first; the trend lines run the whole window.

    1. Contributors 1 ±0 vs prior 12 months
    2. Maintainers 1 +0 joined · −0 left, last 12 months
    3. Bus factor 1 committers behind half the commits
    4. Community-filed 100% of issues opened, last 12 months
    5. Median time to close 711 days first maintainer reply 12 hours
    6. Open backlog 12 of 33 issues ever filed
    1. Issues opened / month 0 · 0 communitymaintainers
    2. Open backlog 12
    3. Contributors / month 0
    4. Commits / month 0
    5. Stars 1,642
    Issue themes, last 12 months
    • features 100%

    Counts from the project's public repository and git history; no individuals are identified. Maintainers are the committers covering 80% of the last year's commits. how we measure this

    Add the badge to your README

    Maintain this project? The badge links readers straight to this page, so they can follow every release here.

    Tracked by Cyber Toolchain Choose a badge style and copy the code →
    browse all tools → score card for your toolchain →