Website Vulnerability Scanner Report
https://www.pintuco.com.co
The Light Website Scanner didn't check for critical issues like SQLi, XSS, Command Injection, XXE, etc. Upgrade to run Deep scans with
40+ tests and detect more vulnerabilities.
Summary
Overall risk level: Risk ratings: Scan information:
Low High: 0 Start time: Jun 18, 2024 / 20:13:49
Medium: 0 Finish time: Jun 18, 2024 / 20:14:45
Low: 6 Scan duration: 56 sec
Info: 13 Tests performed: 19/19
Scan status: Finished
Findings
Missing security header: X-Content-Type-Options CONFIRMED
URL Evidence
Response headers do not include the X-Content-Type-Options HTTP security header
https://www.pintuco.com.co
Request / Response
Details
Risk description:
The risk is that lack of this header could make possible attacks such as Cross-Site Scripting or phishing in Internet Explorer browsers.
Recommendation:
We recommend setting the X-Content-Type-Options header such as X-Content-Type-Options: nosniff .
References:
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-Content-Type-Options
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Missing security header: Content-Security-Policy CONFIRMED
URL Evidence
Response does not include the HTTP Content-Security-Policy security header or meta tag
https://www.pintuco.com.co
Request / Response
Details
Risk description:
The risk is that if the target application is vulnerable to XSS, lack of this header makes it easily exploitable by attackers.
Recommendation:
Configure the Content-Security-Header to be sent with each HTTP response in order to apply the specific policies needed by the
application.
1/5
References:
https://cheatsheetseries.owasp.org/cheatsheets/Content_Security_Policy_Cheat_Sheet.html
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Missing security header: Referrer-Policy CONFIRMED
URL Evidence
Response headers do not include the Referrer-Policy HTTP security header as well as the <meta> tag with name
https://www.pintuco.com.co 'referrer' is not present in the response.
Request / Response
Details
Risk description:
The risk is that if a user visits a web page (e.g. "http://example.com/pricing/") and clicks on a link from that page going to e.g.
"https://www.google.com", the browser will send to Google the full originating URL in the Referer header, assuming the Referrer-Policy
header is not set. The originating URL could be considered sensitive information and it could be used for user tracking.
Recommendation:
The Referrer-Policy header should be configured on the server side to avoid user tracking and inadvertent information leakage. The value
no-referrer of this header instructs the browser to omit the Referer header entirely.
References:
https://developer.mozilla.org/en-US/docs/Web/Security/Referer_header:_privacy_and_security_concerns
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Missing security header: Strict-Transport-Security CONFIRMED
URL Evidence
Response headers do not include the HTTP Strict-Transport-Security header
https://www.pintuco.com.co
Request / Response
Details
Risk description:
The risk is that lack of this header permits an attacker to force a victim user to initiate a clear-text HTTP connection to the server, thus
opening the possibility to eavesdrop on the network traffic and extract sensitive information (e.g. session cookies).
Recommendation:
The Strict-Transport-Security HTTP header should be sent with each HTTPS response. The syntax is as follows:
Strict-Transport-Security: max-age=<seconds>[; includeSubDomains]
The parameter max-age gives the time frame for requirement of HTTPS in seconds and should be chosen quite high, e.g. several months.
A value below 7776000 is considered as too low by this scanner check.
The flag includeSubDomains defines that the policy applies also for sub domains of the sender of the response.
Classification:
CWE : CWE-693
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Robots.txt file found CONFIRMED
URL
2/5
https://www.pintuco.com.co/robots.txt
Details
Risk description:
There is no particular security risk in having a robots.txt file. However, it's important to note that adding endpoints in it should not be
considered a security measure, as this file can be directly accessed and read by anyone.
Recommendation:
We recommend you to manually review the entries from robots.txt and remove the ones which lead to sensitive locations in the website
(ex. administration panels, configuration files, etc).
References:
https://www.theregister.co.uk/2015/05/19/robotstxt/
Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Server software and technology found UNCONFIRMED
Software / Version Category
MySQL Databases
PHP Programming languages
Google Tag Manager Tag managers
Contact Form 7 5.9.5 WordPress plugins
Gutenberg WordPress plugins, Editors
jQuery Migrate 3.4.1 JavaScript libraries
jQuery JavaScript libraries
Moment.js JavaScript libraries
Open Graph Miscellaneous
Priority Hints Performance
WordPress 6.4.3 CMS, Blogs
Popup Maker 1.18.4 WordPress plugins
RSS Miscellaneous
Yoast SEO SEO, WordPress plugins
Details
Risk description:
The risk is that an attacker could use this information to mount specific attacks against the identified software type and version.
Recommendation:
We recommend you to eliminate the information which permits the identification of software platform, technology, server and operating
system: HTTP server headers, HTML meta information, etc.
References:
https://owasp.org/www-project-web-security-testing-guide/stable/4-Web_Application_Security_Testing/01-Information_Gathering/02-
Fingerprint_Web_Server.html
Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
3/5
Security.txt file is missing CONFIRMED
URL
Missing: https://www.pintuco.com.co/.well-known/security.txt
Details
Risk description:
There is no particular risk in not having a security.txt file for your server. However, this file is important because it offers a designated
channel for reporting vulnerabilities and security issues.
Recommendation:
We recommend you to implement the security.txt file according to the standard, in order to allow researchers or users report any security
issues they find, improving the defensive mechanisms of your server.
References:
https://securitytxt.org/
Classification:
OWASP Top 10 - 2013 : A5 - Security Misconfiguration
OWASP Top 10 - 2017 : A6 - Security Misconfiguration
OWASP Top 10 - 2021 : A5 - Security Misconfiguration
Website is accessible.
Nothing was found for vulnerabilities of server-side software.
Nothing was found for client access policies.
Nothing was found for use of untrusted certificates.
Nothing was found for enabled HTTP debug methods.
Nothing was found for enabled HTTP OPTIONS method.
Nothing was found for secure communication.
Nothing was found for directory listing.
Nothing was found for domain too loose set for cookies.
Nothing was found for HttpOnly flag of cookie.
Nothing was found for Secure flag of cookie.
Nothing was found for unsafe HTTP header Content Security Policy.
4/5
Scan coverage information
List of tests performed (19/19)
Starting the scan...
Checking for missing HTTP header - X-Content-Type-Options...
Checking for missing HTTP header - Content Security Policy...
Checking for missing HTTP header - Referrer...
Checking for missing HTTP header - Strict-Transport-Security...
Checking for website technologies...
Checking for vulnerabilities of server-side software...
Checking for client access policies...
Checking for robots.txt file...
Checking for absence of the security.txt file...
Checking for use of untrusted certificates...
Checking for enabled HTTP debug methods...
Checking for enabled HTTP OPTIONS method...
Checking for secure communication...
Checking for directory listing...
Checking for domain too loose set for cookies...
Checking for HttpOnly flag of cookie...
Checking for Secure flag of cookie...
Checking for unsafe HTTP header Content Security Policy...
Scan parameters
Target: https://www.pintuco.com.co
Scan type: Light
Authentication: False
Scan stats
Unique Injection Points Detected: 230
URLs spidered: 2
Total number of HTTP requests: 11
Average time until a response was
371ms
received:
5/5
