> 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/xxe/blind-xxe-with-out-of-band-interaction.md).
# XXE ciego con interacción fuera de banda
Notas de XXE ciego con interacción fuera de banda 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.
### XXE ciego con interacción fuera de banda
La función Comprobar stock acepta un XML, pero **no muestra** la respuesta. Se trata de un XXE ciego: no se ve directamente el contenido devuelto por el analizador. Para detectar y explotar la vulnerabilidad, se generan interacciones fuera de banda (OOB) — por ejemplo, una consulta DNS o una petición HTTP a un dominio controlado (Burp Collaborator / OAST) — para ver si el analizador realiza solicitudes externas.
{% code overflow="wrap" %}
```xml
test
1
```
{% endcode %}
Si se envía este XML, no se obtiene respuesta de la interfaz (comportamiento ciego).
#### Uso de una entidad externa hacia Burp Collaborator
Declare una entidad externa que apunte a un dominio controlado (aquí: `h4m66g65x80x7bwj3ueflms990fr3hr6.oastify.com`) para forzar al analizador a realizar una consulta HTTP/DNS — si la consulta llega al servicio OOB, la aplicación es vulnerable al XXE ciego.
```xml
]>
&myFile;
1
```
Después de enviarlo, vemos la recepción de la solicitud en el servicio OOB (Burp Collaborator), lo que confirma la presencia de un XXE ciego con interacción fuera de banda.
---
# 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/xxe/blind-xxe-with-out-of-band-interaction.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.
