[🚀] Fixes for the coding challenges

[the-pro]

As a new feature is introduced into the juice-shop for selecting the correct code fix for a challenge, we need to write dummy fixes and actual fixes for the challenges. Each fix for each challenge will be written in a separate file. All of the files will be stored in data/static/codefixes. The name of the file will look like this:

• For dummy fixes: <challenge key>_<fix number>.<extension>
• For actual fixes: <challenge key>_<fix number>_correct.<extension>

For any of the challenge listed below, create a 3 or 4 dummy fixes and one correct fix. Indentation of the code of those files should be such that every line doesn't give diff due to the indentation.
Ideally it should look something like this:

The challenges for which these needs to be added are:

• API-only XSS
• Access Log
• Admin Registration
• Admin Section
• Allowlist Bypass
• Arbitrary File Write
• Bjoern's Favorite Pet
• Blockchain Hype
• Bonus Payload
• Confidential Document
• DOM XSS
• Database Schema
• Exposed Metrics
• Forged Review
• Login Admin
• Login Bender
• Login Jim
• NoSQL DoS
• NoSQL Manipulation
• Outdated Allowlist
• Product Tampering
• Repetitive Registration
• Reset Bender's Password
• Reset Bjoern's Password
• Reset Jim's Password
• Reset Morty's Password
• Reset Uvogin's Password
• Score Board
• User Credentials

[github-actions]

This thread has been automatically locked because it has not had recent activity after it was closed. 🔒 Please open a new issue for regressions or related bugs.