> 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/zh/web/sql-injection/sql-injection-in-where-clause.md).

# WHERE 子句中的 SQL 注入

WHERE 子句中的 SQL 注入笔记，适用于 PortSwigger Web Security Academy 实验室，包括利用流程、载荷测试、Burp Suite 验证和修复上下文。

### WHERE 子句中的 SQL 注入漏洞，允许检索隐藏数据

* **背景 / 漏洞：** 类别筛选器存在 SQL 注入漏洞。服务器上执行的典型请求：/ `SELECT * FROM products WHERE category = 'Gifts' AND released = 1`
* \*\*攻击目标（实验室）：\*\*强制显示一个或多个未发布产品（`released = 0`).
* **存在漏洞的参数：** `category` （产品筛选器）。
* **概念验证（提供的载荷）：**

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

* 简要说明：该载荷修改了 WHERE 条件，以包含以下记录： `category='Lifestyle' AND released=0`，从而绕过 `released = 1` 约束。
* **预期结果：** 页面返回并显示对应于 `released = 0` （未发布产品）。
* **影响：** 隐藏元素泄露、可能外泄敏感数据、规避业务逻辑（非面向公众）。


---

# 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/zh/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.