Free Practice Lab
A full, real vulnerable web application — free for everyone. Explore it, find the flaws yourself, and climb the built-in scoreboard. The best way to try ShankarStack before going Pro.
Scenario
This is an open, always-on practice environment: a complete, realistic e-commerce application riddled with real vulnerabilities (OWASP Juice Shop). Nothing hands you the answer — you investigate the app, find the bugs and solve 100+ challenges at your own pace, exactly as you would on a real engagement. A built-in scoreboard tracks what you've solved.
Objective
Explore the hosted vulnerable application, discover and exploit its flaws across the OWASP Top 10, and progress through its challenges using your browser and an intercepting proxy.
Your approach
- Open the hosted lab and use the application like a normal user first.
- Find the hidden score board — locating it is itself the first challenge.
- Work challenges by difficulty, from one star upward.
- Use your browser's developer tools and an intercepting proxy (Burp Suite or OWASP ZAP).
- Read each challenge's built-in hint only when you're stuck — then understand the fix.
Rules of engagement
Run this lab only in the isolated environment provided — the downloadable bundle runs on your own machine in a private Docker network. Only interact with the lab's target, keep testing non-destructive, and never use these techniques on systems you don't own or aren't authorised to test. When you've met the objective, submit the flag (format SS{...}) to score.
Remediation focus
For every flaw you find, be able to state the control that prevents it — parameterised queries, output encoding, server-side authorization, and so on. Finding bugs is half the skill; knowing the fix is what makes you a professional.
Deliverable
Write up what you did, what you observed, the business impact, and a clear remediation — exactly as you would in a professional report.
Hints
Hint 1
Re-read the matching knowledge-base entry before you start.
Hint 2
Capture reproducible evidence as you go — you'll need it for the write-up.
Hint 3
For every finding, identify the single control that would prevent it.