> For the complete documentation index, see [llms.txt](https://hacking-notes.jord4n.pro/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://hacking-notes.jord4n.pro/web/sql-injection/sql-injection-in-where-clause.md).

# SQL Injection in the WHERE Clause

SQL Injection in the WHERE Clause notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### SQL Injection Vulnerability in WHERE Clause Allowing Retrieval of Hidden Data

* **Background / Vulnerability:** Category filter vulnerable to SQL injection. The typical request executed on the server:/ `SELECT * FROM products WHERE category = 'Gifts' AND released = 1`
* \*\*Objective of attack (lab):\*\*force the display of one or more unpublished products (`released = 0`).
* **Vulnerable parameter:** `category` (product filter).
* **Concept proof (payload provided):**

```sql
test' or category='Lifestyle' and released=0-- -
```

* Short interpretation: the payload modifies the WHERE condition to include entries where `category='Lifestyle' AND released=0`, bypassing the `released = 1` constraint.
* **Expected result:** the page returns and displays products corresponding to `released = 0` (unpublished products).
* **Impact:** disclosure of masked elements, potential exfiltration of sensitive data, circumvention of business logic (not intended for the public).


---

# 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://hacking-notes.jord4n.pro/web/sql-injection/sql-injection-in-where-clause.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.