Is www.polypipethailand.com secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

Website security scan results for www.polypipethailand.com

Safe mode. Please [ log in ] to see the full report!

At a glance

------------------
Site scanned: www.polypipethailand.com
Date of scan: June 18, 2022, 4:08 a.m.

Risk level: MEDIUM
SSL Status: [OK] SSL Encryption enforced

Total OWASP ZAP alerts: 72
Nmap open ports found: 18

Server

------------------
IP: 27.254.87.142
Location: Thailand
Web server: nginx/1.9.2

Open ports for www.polypipethailand.com (Nmap scan)

------------------
Port 21 (tcp) - ftp
Port 22 (tcp) - ssh
Port 25 (tcp) - smtp
[ 15 more ]

OWASP ZAP scan results

------------------

Informative alerts

What does this mean?

The response appears to contain suspicious comments which may help an attacker. Note: Matches made within script blocks or files are against the entire content not only comments.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/libs/jquery/3.0.0/jquery.min.js
How to solve this?

Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.

What does this mean?

A timestamp was disclosed by the application/web server - Unix

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/libs/jquery/3.0.0/jquery.min.js
  2. https://www.polypipethailand.com/libs/jquery/3.0.0/jquery.min.js
How to solve this?

Manually confirm that the timestamp data is not sensitive, and that the data cannot be aggregated to disclose exploitable patterns.

Low risk vulnerabilities

What does this mean?

A cookie has been set without the HttpOnly flag, which means that the cookie can be accessed by JavaScript. If a malicious script can be run on this page then the cookie will be accessible and can be transmitted to another site. If this is a session cookie then session hijacking may be possible.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/
  2. https://www.polypipethailand.com/robots.txt
How to solve this?

Ensure that the HttpOnly flag is set for all cookies.

What does this mean?

A cookie has been set without the SameSite attribute, which means that the cookie can be sent as a result of a 'cross-site' request. The SameSite attribute is an effective counter measure to cross-site request forgery, cross-site script inclusion, and timing attacks.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/
  2. https://www.polypipethailand.com/robots.txt
How to solve this?

Ensure that the SameSite attribute is set to either 'lax' or ideally 'strict' for all cookies.

What does this mean?

A cookie has been set without the secure flag, which means that the cookie can be accessed via unencrypted connections.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/
  2. https://www.polypipethailand.com/robots.txt
How to solve this?

Whenever a cookie contains sensitive information or is a session token, then it should always be passed using an encrypted channel. Ensure that the secure flag is set for cookies containing such sensitive information.

What does this mean?

The cache-control and pragma HTTP header have not been set properly or are missing allowing the browser and proxies to cache content.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/styles/stylesheet.css
  2. https://www.polypipethailand.com/styles/social/social.css
  3. https://www.polypipethailand.com/libs/owl-carousel/owl.carousel.css
  4. https://www.polypipethailand.com/styles/uicons/uicons-sr.css
  5. https://www.polypipethailand.com/libs/owl-carousel/owl.theme.css
  6. https://www.polypipethailand.com/libs/menu/css.css
  7. https://www.polypipethailand.com/styles/flaticon/flaticon.css
  8. https://www.polypipethailand.com/styles/responsive.css
How to solve this?

Whenever possible ensure the cache-control HTTP header is set with no-cache, no-store, must-revalidate; and that the pragma HTTP header is set with no-cache.

What does this mean?

The web/application server is leaking information via one or more 'X-Powered-By' HTTP response headers. Access to such information may facilitate attackers identifying other frameworks/components your web application is reliant upon and the vulnerabilities such components may be subject to.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/google-map/
  2. https://www.polypipethailand.com/portfolio/PR00017/
  3. https://www.polypipethailand.com/portfolio/PR00013/
  4. https://www.polypipethailand.com/portfolio/PR00007/
  5. https://www.polypipethailand.com/portfolio/PR00003/
  6. https://www.polypipethailand.com/categories/%E0%B8%A7%E0%B8%B2%E0%B8%A5%E0%B9%8C%E0%B8%A7-TOZEN/
  7. https://www.polypipethailand.com/categories/%E0%B8%A7%E0%B8%B2%E0%B8%A5%E0%B9%8C%E0%B8%A7-CRANE/
  8. https://www.polypipethailand.com/portfolio/PR00010/
  9. https://www.polypipethailand.com/portfolio/PR00018/
  10. https://www.polypipethailand.com/contact-us/
  11. https://www.polypipethailand.com/portfolio/PR00014/
  12. https://www.polypipethailand.com/portfolio/
  13. https://www.polypipethailand.com/portfolio/PR00004/
  14. https://www.polypipethailand.com/portfolio/PR00008/
  15. https://www.polypipethailand.com/categories/PP-R-pipe/
  16. https://www.polypipethailand.com/portfolio/PR00015/
  17. https://www.polypipethailand.com/portfolio/PR00011/
  18. https://www.polypipethailand.com/categories/Valves/
  19. https://www.polypipethailand.com/portfolio/PR00019/
  20. https://www.polypipethailand.com/categories/HDPE-pipe/
How to solve this?

Ensure that your web server, application server, load balancer, etc. is configured to suppress 'X-Powered-By' headers.

What does this mean?

The Anti-MIME-Sniffing header X-Content-Type-Options was not set to 'nosniff'. This allows older versions of Internet Explorer and Chrome to perform MIME-sniffing on the response body, potentially causing the response body to be interpreted and displayed as a content type other than the declared content type. Current (early 2014) and legacy versions of Firefox will use the declared content type (if one is set), rather than performing MIME-sniffing.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/portfolio/PR00002/
  2. https://www.polypipethailand.com/upload/posts/logo/PR00017.jpg
  3. https://www.polypipethailand.com/icons.png
  4. https://www.polypipethailand.com/portfolio/PR00006/
  5. https://www.polypipethailand.com/upload/posts/logo/PR00011.jpg
  6. https://www.polypipethailand.com/portfolio/PR00013/
  7. https://www.polypipethailand.com/portfolio/PR00017/
  8. https://www.polypipethailand.com/upload/posts/logo/PR00012.jpg
  9. https://www.polypipethailand.com/contact-us/
  10. https://www.polypipethailand.com/google-map/
  11. https://www.polypipethailand.com/styles/uicons/uicons-sr.css
  12. https://www.polypipethailand.com/upload/posts/logo/PR00015.jpg
  13. https://www.polypipethailand.com/images/qr-code.png
  14. https://www.polypipethailand.com/portfolio/PR00001/
  15. https://www.polypipethailand.com/upload/posts/logo/PR00014.jpg
  16. https://www.polypipethailand.com/portfolio/PR00005/
  17. https://www.polypipethailand.com/portfolio/PR00020/
  18. https://www.polypipethailand.com/libs/jquery/3.0.0/jquery.min.js
  19. https://www.polypipethailand.com/portfolio/PR00009/
  20. https://www.polypipethailand.com/libs/owl-carousel/owl.carousel.css
How to solve this?

Ensure that the application/web server sets the Content-Type header appropriately, and that it sets the X-Content-Type-Options header to 'nosniff' for all web pages.If possible, ensure that the end user uses a standards-compliant and modern web browser that does not perform MIME-sniffing at all, or that can be directed by the web application/web server to not perform MIME-sniffing.

Medium risk vulnerabilities

What does this mean?

The identified library jquery, version 3.0.0 is vulnerable.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/libs/jquery/3.0.0/jquery.min.js
How to solve this?

Please upgrade to the latest version of jquery.

What does this mean?

X-Frame-Options header is not included in the HTTP response to protect against 'ClickJacking' attacks.

Where exactly is this vulnerability found?
  1. https://www.polypipethailand.com/portfolio/PR00002/
  2. https://www.polypipethailand.com/portfolio/PR00017/
  3. https://www.polypipethailand.com/portfolio/PR00013/
  4. https://www.polypipethailand.com/
  5. https://www.polypipethailand.com/portfolio/PR00005/
  6. https://www.polypipethailand.com/portfolio/PR00009/
  7. https://www.polypipethailand.com/portfolio/PR00020/
  8. https://www.polypipethailand.com/portfolio/PR00001/
  9. https://www.polypipethailand.com/google-map/
  10. https://www.polypipethailand.com/portfolio/PR00016/
  11. https://www.polypipethailand.com/portfolio/PR00012/
  12. https://www.polypipethailand.com/portfolio/PR00008/
  13. https://www.polypipethailand.com/contact-us/
  14. https://www.polypipethailand.com/portfolio/PR00004/
  15. https://www.polypipethailand.com/about-us/
  16. https://www.polypipethailand.com/portfolio/PR00019/
  17. https://www.polypipethailand.com/portfolio/PR00011/
  18. https://www.polypipethailand.com/portfolio/PR00015/
  19. https://www.polypipethailand.com/portfolio/PR00007/
  20. https://www.polypipethailand.com/portfolio/PR00003/
How to solve this?

Most modern Web browsers support the X-Frame-Options HTTP header. Ensure it's set on all web pages returned by your site (if you expect the page to be framed only by pages on your server (e.g. it's part of a FRAMESET) then you'll want to use SAMEORIGIN, otherwise if you never expect the page to be framed, you should use DENY. ALLOW-FROM allows specific websites to frame the web page in supported web browsers).

High risk vulnerabilities

Manual inspection results

This site has not been manually inspected yet. Please apply for an inspection here

Find this WSO report online:

Environment info

------------------

Technology

JQuery (3.0.0)
Apache (2)
PHP (5.6.40)
nginx (1.9.2)

Other

Open-Graph-Protocol (website)
Script (['text/javascript'])
UncommonHeaders (upgrade)
HTML5
Cookies (PHPSESSID)
X-Powered-By (PHP/5.6.40)
Email (['polypipe2539@gmail.com'])
[ 3 more ]
See hacks, ports, leaked data and possible attack routes for www.polypipethailand.com

Idyllum Labs is on a mission

------------------

Is the code hosted at www.polypipethailand.com vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2022?

We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.

Please note

This is an automated and unbiased website vulnerability scan for the domain www.polypipethailand.com and has nothing to do with human subjectivity, thoughts, opinions, or relationships.

Our cloud-based infrastructure crawls the internet using a mixture of OWASP ZAP, Nmap, Whatweb, and other great software to detect website security issues. We display this data for educational purposes - to give security guidelines for anyone interested in building a safer web environment.

If you have comments, don't agree with the results, or want to submit a site for manual examination, don't hesitate to contact us.


Run a free OWASP ZAP scan for any website at Idyllum.com!

What next?

------------------

Dig deeper

  1. Log in or create a free account to gain access to this report in its entirety.
  2. Use our dashboard to automate security testing and set up automatic monitoring for your website portfolio.
  3. Scan a new domain or initiate a rescan for this domain.

Join our ranks

  1. Use these insights to build your systems bullet-proof.
  2. Explore our datasets and compare your results.
  3. Drop us a line! Help us expand our code or cloud or just say hi!
  4. Support the cause - your donation helps to keep this service free and unbiased.