Wapiti vulnerability report

Target: https://pentest-ground.com:81/

Date of the scan: Mon, 16 Mar 2026 20:43:45 +0000. Scope of the scan: folder

Summary

Category Number of vulnerabilities found
Backup file 0
Blind SQL Injection 0
Weak credentials 0
CRLF Injection 0
Content Security Policy Configuration 1
Cross Site Request Forgery 0
Potentially dangerous file 0
Command execution 0
Path Traversal 0
Htaccess Bypass 0
HTTP Secure Headers 4
HttpOnly Flag cookie 1
Open Redirect 0
Secure Flag cookie 1
SQL Injection 0
Server Side Request Forgery 0
Cross Site Scripting 2
XML External Entity 0
Internal Server Error 0
Resource consumption 0
Fingerprint web technology 0

Content Security Policy Configuration

Description
Content Security Policy (CSP) is an added layer of security that helps to detect and mitigate certain types of attacks, including Cross Site Scripting (XSS) and data injection attacks.

Vulnerability found in /

CSP is not set
Solutions
Configuring Content Security Policy involves adding the Content-Security-Policy HTTP header to a web page and giving it values to control what resources the user agent is allowed to load for that page.
References

HTTP Secure Headers

Description
HTTP security headers tell the browser how to behave when handling the website's content.

Vulnerability found in /

X-Frame-Options is not set

Vulnerability found in /

X-XSS-Protection is not set

Vulnerability found in /

X-Content-Type-Options is not set

Vulnerability found in /

Strict-Transport-Security is not set
Solutions
Use the recommendations for hardening your HTTP Security Headers.
References

HttpOnly Flag cookie

Description
HttpOnly is an additional flag included in a Set-Cookie HTTP response header. Using the HttpOnly flag when generating a cookie helps mitigate the risk of client side script accessing the protected cookie (if the browser supports it).

Vulnerability found in /

HttpOnly flag is not set in the cookie : SessionID
Solutions
While creation of the cookie, make sure to set the HttpOnly Flag to True.
References

Secure Flag cookie

Description
The secure flag is an option that can be set by the application server when sending a new cookie to the user within an HTTP Response. The purpose of the secure flag is to prevent cookies from being observed by unauthorized parties due to the transmission of a the cookie in clear text.

Vulnerability found in /

Secure flag is not set in the cookie : SessionID
Solutions
When generating the cookie, make sure to set the Secure Flag to True.
References

Cross Site Scripting

Description
Cross-site scripting (XSS) is a type of computer security vulnerability typically found in web applications which allow code injection by malicious web users into the web pages viewed by other users. Examples of such code include HTML code and client-side scripts.

Vulnerability found in /1/edit

XSS vulnerability found via injection in the parameter title

Vulnerability found in /2/edit

XSS vulnerability found via injection in the parameter title
Solutions
The best way to protect a web application from XSS attacks is ensure that the application performs validation of all headers, cookies, query strings, form fields, and hidden fields. Encoding user supplied output in the server side can also defeat XSS vulnerabilities by preventing inserted scripts from being transmitted to users in an executable form. Applications can gain significant protection from javascript based attacks by converting the following characters in all generated output to the appropriate HTML entity encoding:<, >, &, ', (, ), #, %, ; , +, -
References