> For the complete documentation index, see [llms.txt](https://ganesha-hk.gitbook.io/offensive-security-writeups/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://ganesha-hk.gitbook.io/offensive-security-writeups/port-swigger-ssti-labs/lab-4.md).

# lab-4

## Server-Side Template Injection with Information Disclosure via User-Supplied Objects

**Difficulty:** Practitioner

### Lab Description

This lab is vulnerable to server-side template injection due to the way an object is passed into the template, which can be exploited to access sensitive data.

**Objective:** Steal and submit the framework's secret key.

**Credentials:** `content-manager:C0nt3ntM4n4g3r`

### Solution

**Step 1 — Locate the editable template**

Log in with the provided credentials, go to a product page, and edit its template.

**Step 2 — Confirm the template engine**

Change the existing `{{productstock}}` placeholder to:

```django
{{ 7*7 }}
```

The response shows `49`, and the error/behavior patterns confirm the backend is using the **Django** template engine.

**Step 3 — Use a debug built-in to enumerate context objects**

Django templates expose a built-in debug tag that discloses every object available in the rendering context:

```django
{% debug %}
```

Reviewing the disclosed objects reveals a `settings` object is accessible, which can be used to read the framework's secret key:

```django
{{ settings.SECRET_KEY }}
```

### Conclusion

Passing a raw settings/config object into the template context — rather than only the specific values needed — gave an attacker indirect read access to sensitive application secrets through Django's own debugging built-ins.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://ganesha-hk.gitbook.io/offensive-security-writeups/port-swigger-ssti-labs/lab-4.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.