System File Compromise: It is possible to access system files by injecting input parameters with the pathnames of system files. The web application will fetch the system files instead of application files. The system files may be displayed and/or included in page output. Remember web applications are usually served from a system directory like /var/www or C:XAMPP. You may need to move up directories.

HTML Injection: It is possible to inject your own HTML into this page because the input is not encoded prior to be used as output. Determine which input field contributes output here and inject HTML, CSS, and/or Javascripts in order to alter the client-side code of this page.

Insecure Direct Object Reference: This page refers directly to resources by there real name or identifier making it possible to modify the name/ID to access other resources. Determine what resources are fetched. Provide the name or ID of a different resource. Resources can be filenames, record identifiers or others.

Server Side Include: It is possible to make the application include application files in this page that are not intended. These files may even come from other sites.

Local File Inclusion: This page is vulnerable to local file inclusion if the user account under which PHP is running has access to files besides the intended web site files.

Remote File Inclusion: This page is vulnerable to remote file inclusion if the PHP server configuration parameters "allow_url_fopen" and "allow_url_include" are set to "On" in php.ini.

Reflected Cross-Site Scripting: This page is vulnerable to reflected cross-site scripting because the input is not encoded prior to be used as output. Determine which input field contributes output here and inject scripts. Try to redirect the user to the capture-data.php page which records cookies and other parameters. Visit the captured-data.php page to view captured data.