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

# Inyección SQL en la cláusula WHERE

Notas de Inyección SQL en la cláusula WHERE para laboratorios de PortSwigger Web Security Academy, incluido el flujo de explotación, pruebas de payloads, validación con Burp Suite y contexto de remediación.

### Vulnerabilidad de inyección SQL en la cláusula WHERE que permite recuperar datos ocultos

* **Contexto / Vulnerabilidad:** El filtro de categoría es vulnerable a inyección SQL. La solicitud típica ejecutada en el servidor:/ `SELECT * FROM products WHERE category = 'Gifts' AND released = 1`
* \*\*Objetivo del ataque (laboratorio):\*\*forzar la visualización de uno o más productos no publicados (`released = 0`).
* **Parámetro vulnerable:** `category` (filtro de productos).
* **Prueba de concepto (payload proporcionado):**

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

* Interpretación breve: el payload modifica la condición WHERE para incluir entradas donde `category='Lifestyle' AND released=0`, eludiendo la `released = 1` restricción.
* **Resultado esperado:** la página devuelve y muestra productos correspondientes a `released = 0` (productos no publicados).
* **Impacto:** divulgación de elementos ocultos, posible exfiltración de datos sensibles, elusión de la lógica de negocio (no destinada al público).


---

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