Is studio-y-creation.net secure and safe to use? | Web Security Optimization (WSO) report by Idyllum Labs.

bot@idyllum:~$ Please wait, the scan will start shortly

bot@idyllum:~$ Scanning: /100

bot@idyllum:~$ Latest scan is in long queue and may take a while

bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again

This site redirects to

Invalid domain!

Please log in or sign up for a free account to see this report in its entirety!

# Website security scan results for studio-y-creation.net

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

## At a glance

Site scanned: studio-y-creation.net
Risk level: MEDIUM
WSO score: 85 / 100
Ranks: worse than 75.7% of tested sites
Date of scan: Sept. 19, 2021, 4:15 a.m.
SSL Status: [OK] SSL Encryption enforced
Total alerts: 94

## Verdict

Average! This website can be considered safe. But there is room for easy improvement! Please forward this report to the web development team and we are sure they can find some ways to secure the site even more.

# Environment info

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

## Server

IP: 52.196.70.116
Location: UNITED STATES
Web server: nginx

## Technology

nginx

# 2 Open ports for studio-y-creation.net (Nmap scan)

------------------
Port 80 (tcp) - http
Port 443 (tcp) - https

# OWASP ZAP scan results

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

## Informative alerts

[!!] FAILED Information Disclosure - Suspicious Comments
[+]
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://studio-y-creation.net/
  2. https://studio-y-creation.net/items/60e42e839bb167434d33d352
  3. https://studio-y-creation.net/items/606560c7d263f04067090af1
  4. https://studio-y-creation.net/items/60656077baeb3a72c9aeabb3
  5. https://studio-y-creation.net/items/606560241e746b7ef5c974dd
  6. https://studio-y-creation.net/checkout_rakuten_pay_error
  7. https://studio-y-creation.net/items/60655d94d5e9c9531cf02aab
  8. https://studio-y-creation.net/?all_items=true
  9. https://studio-y-creation.net/inquiry
  10. https://studio-y-creation.net/?category_id=5d81d332b02f292e87ce4603
  11. https://studio-y-creation.net/items/6034af496728be7c6893700a
  12. https://studio-y-creation.net/privacy_policy
  13. https://studio-y-creation.net/items/60e437cda1ea7c5bdc6c8d81
  14. https://studio-y-creation.net/?category_id=6064931cd263f034d9695698
  15. https://studio-y-creation.net/items/60e43ea4a1ea7c31536c8a79
  16. https://studio-y-creation.net/sale
  17. https://studio-y-creation.net/items/60e2c74b0850a037dfb05fb4
  18. https://studio-y-creation.net/assets/stores/common/application_header-406fd773749353fb6cb2fe0f0da708bc04dad5928a2215974055a596a23e63b2.js
  19. https://studio-y-creation.net/packs/js/stores/redirect-9339ca17a994cb4720eb.js
  20. https://studio-y-creation.net/items/60e2c3f2a00a4a36cc77d05b
How to solve this?

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

[!!] FAILED Timestamp Disclosure - Unix
[+]
What does this mean?

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

Where exactly is this vulnerability found?
  1. https://studio-y-creation.net/packs/js/stores/redirect-9339ca17a994cb4720eb.js
  2. https://studio-y-creation.net/items/60e2c3f2a00a4a36cc77d05b
  3. https://studio-y-creation.net/items/60e2c7070850a037c9b05f95
  4. https://studio-y-creation.net/items/606549aed5e9c9535cf024b5
  5. https://studio-y-creation.net/?category_id=5d81d3621b6b76213b324219
  6. https://studio-y-creation.net/items/60e2c463a00a4a36c877d04a
  7. https://studio-y-creation.net/items/60e2c21cf56851122e9f21cc
  8. https://studio-y-creation.net/?category_id=5d81d39c6004fb23bf110374
  9. https://studio-y-creation.net/items/60e43eebc3289c641809d735
  10. https://studio-y-creation.net/signup/register
  11. https://studio-y-creation.net/tokushoho
  12. https://studio-y-creation.net/items/60e43dedc3289c641809d6e8
  13. https://studio-y-creation.net/assets/stores/common/application_header-406fd773749353fb6cb2fe0f0da708bc04dad5928a2215974055a596a23e63b2.js
  14. https://studio-y-creation.net/packs/js/stores/redirect-9339ca17a994cb4720eb.js
  15. https://studio-y-creation.net/assets/stores/responsive/show_application-fd65b7efa72ff0d4b8e86cfeae31fd550da50a339e121208e2f227ce7fd70275.css
  16. https://studio-y-creation.net/?category_id=5e1e7df7fa03d7102af00b9b
  17. https://studio-y-creation.net/items/60655fcc23055713483448d3
  18. https://studio-y-creation.net/about
  19. https://studio-y-creation.net/packs/js/stores/redirect-9339ca17a994cb4720eb.js
  20. https://studio-y-creation.net/?category_id=5d81d5716004fb2450110497
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

[!!] FAILED Cookie Without SameSite Attribute
[+]
What does this mean?

A cookie has been set with an invalid SameSite attribute value, 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://studio-y-creation.net/items/60e2c21cf56851122e9f21cc
  2. https://studio-y-creation.net/reset_password
  3. https://studio-y-creation.net/?category_id=5d5a68670838297b18262eea
  4. https://studio-y-creation.net/items/60e2c67059a26c6e906271bc
  5. https://studio-y-creation.net/items/60e2c3f2a00a4a36cc77d05b
  6. https://studio-y-creation.net/items/606549aed5e9c9535cf024b5
  7. https://studio-y-creation.net/items/60e437cda1ea7c5bdc6c8d81
  8. https://studio-y-creation.net/checkout_amazon_pay
  9. https://studio-y-creation.net/?category_id=5d81d3621b6b76213b324219
  10. https://studio-y-creation.net/?category_id=5d81d4b71c77073542758c30
  11. https://studio-y-creation.net/?category_id=5e1e7df7fa03d7102af00b9b
  12. https://studio-y-creation.net/iframe
  13. https://studio-y-creation.net/items/6034af496728be7c6893700a
  14. https://studio-y-creation.net/emails
  15. https://studio-y-creation.net/?all_items=true
  16. https://studio-y-creation.net/items/606560c7d263f04067090af1
  17. https://studio-y-creation.net/checkout_rakuten_pay_error
  18. https://studio-y-creation.net/items/60e2c4f3561e17460a379c25
  19. https://studio-y-creation.net/items/60656077baeb3a72c9aeabb3
  20. https://studio-y-creation.net/inquiry
How to solve this?

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

[!!] FAILED Incomplete or No Cache-control and Pragma HTTP Header Set
[+]
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://studio-y-creation.net/items/60e2c463a00a4a36c877d04a
  2. https://studio-y-creation.net/items/60e43eebc3289c641809d735
  3. https://studio-y-creation.net/tokushoho
  4. https://studio-y-creation.net/signup/register
  5. https://studio-y-creation.net/items/60e43dedc3289c641809d6e8
  6. https://studio-y-creation.net/items/60655fcc23055713483448d3
  7. https://studio-y-creation.net/?category_id=6064931cd263f034d9695698
  8. https://studio-y-creation.net/?category_id=5d81d5716004fb2450110497
  9. https://studio-y-creation.net/items/60e43ea4a1ea7c31536c8a79
  10. https://studio-y-creation.net/?category_id=5d81d39c6004fb23bf110374
  11. https://studio-y-creation.net/sale
  12. https://studio-y-creation.net/items/60e2c7070850a037c9b05f95
  13. https://studio-y-creation.net/items/60e2c74b0850a037dfb05fb4
  14. https://studio-y-creation.net/error_pages/images/common/logo_white.svg
  15. https://studio-y-creation.net/?category_id=5d81d3621b6b76213b324219
  16. https://studio-y-creation.net/items/60655f73d5e9c9532bf02b35
  17. https://studio-y-creation.net/privacy_policy
  18. https://studio-y-creation.net/items/606493231e746b13c37a07db
  19. https://studio-y-creation.net/items/606560241e746b7ef5c974dd
  20. https://studio-y-creation.net/checkout_rakuten_pay_error
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.

[!!] FAILED X-Content-Type-Options Header Missing
[+]
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://studio-y-creation.net/error_pages/images/common/logo_white.svg
  2. https://studio-y-creation.net/assets/stores/common/application_header-406fd773749353fb6cb2fe0f0da708bc04dad5928a2215974055a596a23e63b2.js
  3. https://studio-y-creation.net/packs/css/stores/top-14610ab8.css
  4. https://studio-y-creation.net/images/icon/icon_store_favicon.ico
  5. https://studio-y-creation.net/assets/stores/responsive/show_application-fd65b7efa72ff0d4b8e86cfeae31fd550da50a339e121208e2f227ce7fd70275.css
  6. https://studio-y-creation.net/packs/js/stores/redirect-9339ca17a994cb4720eb.js
  7. https://studio-y-creation.net/error_pages/images/404/404.png
  8. https://studio-y-creation.net/error_pages/styles/404/main.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.

[!!] FAILED Absence of Anti-CSRF Tokens
[+]
What does this mean?

No Anti-CSRF tokens were found in a HTML submission form.A cross-site request forgery is an attack that involves forcing a victim to send an HTTP request to a target destination without their knowledge or intent in order to perform an action as the victim. The underlying cause is application functionality using predictable URL/form actions in a repeatable way. The nature of the attack is that CSRF exploits the trust that a web site has for a user. By contrast, cross-site scripting (XSS) exploits the trust that a user has for a web site. Like XSS, CSRF attacks are not necessarily cross-site, but they can be. Cross-site request forgery is also known as CSRF, XSRF, one-click attack, session riding, confused deputy, and sea surf.CSRF attacks are effective in a number of situations, including: * The victim has an active session on the target site. * The victim is authenticated via HTTP auth on the target site. * The victim is on the same local network as the target site.CSRF has primarily been used to perform an action against a target site using the victim's privileges, but recent techniques have been discovered to disclose information by gaining access to the response. The risk of information disclosure is dramatically increased when the target site is vulnerable to XSS, because XSS can be used as a platform for CSRF, allowing the attack to operate within the bounds of the same-origin policy.

Where exactly is this vulnerability found?
  1. https://studio-y-creation.net/inquiry
  2. https://studio-y-creation.net/checkout
  3. https://studio-y-creation.net/checkout
  4. https://studio-y-creation.net/checkout
  5. https://studio-y-creation.net/checkout
How to solve this?

Phase: Architecture and DesignUse a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid.For example, use anti-CSRF packages such as the OWASP CSRFGuard.Phase: ImplementationEnsure that your application is free of cross-site scripting issues, because most CSRF defenses can be bypassed using attacker-controlled script.Phase: Architecture and DesignGenerate a unique nonce for each form, place the nonce into the form, and verify the nonce upon receipt of the form. Be sure that the nonce is not predictable (CWE-330).Note that this can be bypassed using XSS.Identify especially dangerous operations. When the user performs a dangerous operation, send a separate confirmation request to ensure that the user intended to perform that operation.Note that this can be bypassed using XSS.Use the ESAPI Session Management control.This control includes a component for CSRF.Do not use the GET method for any request that triggers a state change.Phase: ImplementationCheck the HTTP Referer header to see if the request originated from an expected page. This could break legitimate functionality, because users or proxies may have disabled sending the Referer for privacy reasons.

[!!] FAILED Cookie Without Secure Flag
[+]
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://studio-y-creation.net/
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.

## Medium risk vulnerabilities

[!!] FAILED CSP: Wildcard Directive
[+]
What does this mean?

The following directives either allow wildcard sources (or ancestors), are not defined, or are overly broadly defined: script-src, script-src-elem, script-src-attr, style-src, style-src-elem, style-src-attr, img-src, connect-src, frame-src, font-src, media-src, object-src, manifest-src, worker-src, prefetch-src, form-actionThe directive(s): form-action are among the directives that do not fallback to default-src, missing/excluding them is the same as allowing anything.

Where exactly is this vulnerability found?
  1. https://studio-y-creation.net/?category_id=5e1e7df7fa03d7102af00b9b
  2. https://studio-y-creation.net/?category_id=5d81d3621b6b76213b324219
  3. https://studio-y-creation.net/checkout_amazon_pay
  4. https://studio-y-creation.net/?category_id=5d81d4b71c77073542758c30
  5. https://studio-y-creation.net/items/60e2c3f2a00a4a36cc77d05b
  6. https://studio-y-creation.net/items/606549aed5e9c9535cf024b5
  7. https://studio-y-creation.net/?category_id=5d5a68670838297b18262eea
  8. https://studio-y-creation.net/items/60e2c21cf56851122e9f21cc
  9. https://studio-y-creation.net/emails
  10. https://studio-y-creation.net/inquiry
  11. https://studio-y-creation.net/items/60e2c6cac3289c524a85ee26
  12. https://studio-y-creation.net/items/60e2c67059a26c6e906271bc
  13. https://studio-y-creation.net/items/60655fcc23055713483448d3
  14. https://studio-y-creation.net/?all_items=true
  15. https://studio-y-creation.net/items/60e437cda1ea7c5bdc6c8d81
  16. https://studio-y-creation.net/items/60e2c4f3561e17460a379c25
  17. https://studio-y-creation.net/checkout_rakuten_pay_error
  18. https://studio-y-creation.net/tokushoho
  19. https://studio-y-creation.net/items/606560241e746b7ef5c974dd
  20. https://studio-y-creation.net/items/606493231e746b13c37a07db
How to solve this?

Ensure that your web server, application server, load balancer, etc. is properly configured to set the Content-Security-Policy header.

Manual inspection results

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

Find this WSO report online:

# Idyllum Labs is on a mission

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

Is the code hosted at studio-y-creation.net vulnerable to cybersecurity attacks? Are the used systems up to date and respecting the security standards of 2021?

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 studio-y-creation.net 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.

It is important to understand that we don't gather business information. We analyze used technology and are not interested in

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.

Want to scan and monitor multiple sites at once?

Create an account
Yes, generating security reports with Idyllum Labs is free!
(Just as all the best things in life..)