> For the complete documentation index, see [llms.txt](https://sec88.0x88.online/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://sec88.0x88.online/web-appsec/host-header-injection.md).

# Host Header Attacks

## Checklist

* [ ] [**Web cache poisoning via ambiguous requests**](https://portswigger.net/web-security/host-header/exploiting/lab-host-header-web-cache-poisoning-via-ambiguous-requests)
* [ ] [Password reset poisoning](https://portswigger.net/web-security/host-header/exploiting/password-reset-poisoning)
  * [ ] Add two `HOST:` in Request.
  * [ ] Try [localhost](http://localhost)
  * [ ] Try this Headers
  * [ ] If you come across `/api.json` in any AEM instance during bug hunting, try for web cache poisoning via following`Host: , X-Forwarded-Server , X-Forwarded-Host:`\
    and or simply try <https://localhost/api.json> HTTP/1.1
  * [ ] Also try `Host: redacted.com.evil.com`
  * [ ] Try Host: [evil.com/redacted.com](http://evil.com/redacted.com)\
    <https://hackerone.com/reports/317476>
  * [ ] Try this too `Host: example.com?.mavenlink.com`
  * [ ] Try `Host: javascript:alert(1);` Xss payload might result in debugging mode.\
    <https://blog.bentkowski.info/2015/04/xss-via-host-header-cse.html>
  * [ ] Host Header to Sqli\
    <https://blog.usejournal.com/bugbounty-database-hacked-of-indias-popular-sports-company-bypassing-host-header-to-sql-7b9af997c610>
  * [ ] Bypass front server restrictions and access to forbidden files and directories through
  * [ ] Add line wrapping
  * [ ] Supply an absolute URL
* [ ] [Web cache poisoning](https://portswigger.net/web-security/host-header/exploiting#web-cache-poisoning-via-the-host-header)
* [ ] [Exploiting classic server-side vulnerabilities](https://portswigger.net/web-security/host-header/exploiting#exploiting-classic-server-side-vulnerabilities)
* [ ] [Bypassing authentication](https://portswigger.net/web-security/host-header/exploiting#accessing-restricted-functionality)
* [ ] [Virtual host brute-forcing](https://portswigger.net/web-security/host-header/exploiting#accessing-internal-websites-with-virtual-host-brute-forcing)
* [ ] [Routing-based SSRF](https://portswigger.net/web-security/host-header/exploiting#routing-based-ssrf)
* [ ] [Connection state attacks](https://portswigger.net/web-security/host-header/exploiting#connection-state-attacks)

### References

* [PortSwigger](https://portswigger.net/web-security/host-header/exploiting)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://sec88.0x88.online/web-appsec/host-header-injection.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.
