> 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/business-logic/inconsistent-security-controls.md).
# Inconsistent Security Controls
Inconsistent Security Controls notes for PortSwigger Web Security Academy labs, including exploitation workflow, payload testing, Burp Suite validation, and remediation context.
### Inconsistent Security Controls
**Lab objective**
This lab has a logical flaw associated with inconsistent safety checks. / Arbitrary users can access administrative features normally reserved for company employees. / The goal is to access the administration panel and delete the user **carlos**.
**Observation initiale**
When attempting to access the administration interface directly, the following message will appear:
> *Admin interface only available if logged in as a DontWannaCry user*
Access to `/admin` is therefore restricted to users belonging to the **DontWannaCry** domain.
**Registration attempt**
A new user is registered using:
* **User name**: `DontWannaCry` (already existing)
* **Email address**: an address controlled by the attacker/ `attacker@exploit-0a2500bc04ce231c81841ade012e0049.exploit-server.net`
After submitting the form, the application indicates:
> *Please check your emails for your account registration link*
**Account Validation**
A confirmation email is received with a link containing a token.
The credentials used are:
* **User**: `DontWannaCry`
* **Password**: `jordan`
The connection works properly.
**Email Address Modification**
Once logged in, you change the account email address without any additional validation, using:
```bash
jordan@dontwannacry.com
```
There is no control over the legitimacy of this change.
**Access to the administration interface**
After changing the email, the user is now considered to belong to the domain **DontWannaCry**. / Access to the `/admin` interface is then allowed.
---
# 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/business-logic/inconsistent-security-controls.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.
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)
.png?alt=media)