As usual, we can check the way the website works and how it behaves
It is the good old trusted typing practice
Since there is not much functionality apart from the practice, we can check what is BurpSuite showing
First thing to notice is the /v2/login … if there is a v2 … there definitely used to be /v1
This confirms it
With the helpful script mentioned before, we can enumerate more without guessing
Endpoint checker
Endpoints Found: 21
This is interesting
Apart from the /v1, we also find multiple /v2 endpoints with admin and flag
Now the question is how we can get there
I thought this was as simple as this …
I knew it felt too easy …
JWT token
I tried multiple /v2 ways but was not able to move forward
I tried with /v1 since I felt this could be at least worth to test
I simply used the token I had and of course it did not work, but this time, I knew JSON Web Token option in Burp was open
With this I have tried to abuse it in the simplest way, by changing the role from user to admin
That still did not work
This time I thought of two things … either changing the "id": 4 or simply changing alg : none
The id = 1 worked like a charm
MCP attempt
Here I wanted to see the approach from MCP server within Burp
I gave it some options but wanted to see how far it can take me
It struggled to find a way in…
I was still a firm believer it was able to accomplish it, even thought I felt it started to go away from the goal, more trying to overcomplicate its own existence …
At some point though, it started to show some promise!
Found its limitation and helped it with the token I have already created previously
When given a hand, it was able to work it out …
The whole MCP journey for me with Burp is brand new and I see its huge potential for sure!
Keep learning and be useful!
Security Takeaways
Impact
Unauthorized access to admin‑only endpoints and sensitive data
Privilege escalation by modifying client‑controlled JWT claims
Demonstrates broken authorization at the API layer
The backend trusts client‑supplied JWT claims (e.g., role/id) without validating them against server‑side authorization logic, allowing users to escalate privileges.
Remediation
Never trust JWT claims alone for authorization decisions
Re‑validate user roles/permissions server‑side on every request
Enforce strict JWT signing and verification (reject alg: none)
Use least‑privilege roles and separate admin endpoints