bot@idyllum:~$ Please wait, the scan will start shortly
bot@idyllum:~$ Scanning: /100
bot@idyllum:~$ Web Security Optimization (WSO) scan failed! Please try again
This site redirects to
By ignoring this a user of your website could have their accounts completely taken over by clicking on a malicious link and doing nothing else
By ignoring this a user of your website could have their accounts completely taken over by clicking on a malicious link and doing nothing elseWhat does this mean?
"In a Cross-site request forgery (CSRF) attack, an innocent end user is tricked by an attacker into submitting a web request that they did not intend. This may cause actions to be performed on the website that can include client or server data leakage, change of session state, or manipulation of an end user's account. A cross-site request forgery (CSRF) ( often pronounces sea surf) Without Anti-CSRF (often pronounces sea surf) tokens a malicious site may be able to completely take over your users account. Actions that the malicious site may be able to do can include changing the password or email address of the user, making a purchase or any other user controllable action. This attack can ba launched when a user clicks on a malicious link while logged in to your website in the same web browser."
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?
"Many modern content management systems add these automatically to all user inputs including forms available on the public site. If your site is running on an older CMS version, then simply migrating to the latest release could solve the problem. If you are implementing a custom solution, we would recommend implementing anti-CSRF tokens using a well-known framework or library. As an example, the popular php framworks Laravel and Symfony both include out of the box support for anti-CSRF tokens. Additionally, make sure your application does not use GET requests for actions that change the user account or state. GET requests expose their content in the URL itself and therefore can leak your Anti-CSRF token, which should be considered secret. Therefore, GET requests are not protected by anti-CSRF tokens."
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.Real world example
"Both Netflix and YouTube were susceptible to CSRF attacks in their early years. In both cases this allowed any attacker to perform nearly all actions of any user - change account information, user details or even fully compromise the account. In 2019 Facebook awarded $25 000 to a security expert who discovered a CSRF vulnerability in their system. According to the researcher, the exploit could have been used to immediately take over user's Facebook account the moment they clicked on a malicious link while logged into Facebook in the same browser."
The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.
The source code of the tested site contains comments which may contain sensitive data. Like parts of code, url-s or program logic. This could give valuable hints to the potential attacker.What does this mean?
An attacker who finds these comments can map the application's structure and files, expose hidden parts of the site, and study the fragments of code to reverse engineer the application, which may help develop further attacks against the site.
The response appears to contain suspicious comments which may help an attacker.Where exactly is this vulnerability found?
We recommend inspecting your source code (even with your browser). Search for words like "BUG", "HACK", "FIXME", "LATER", "TODO" etc. The issues should be clearly visible.
Remove all comments that return information that may help an attacker and fix any underlying problems they refer to.Real world example
Comments in code are not dangerous themselves. But if a comment gives an attacker hints about system architecture, SQL injections can soon follow. For Yahoo, this caused the loss of 450,000 login credentials back in 2012.
This site has not been manually inspected yet. Please apply for an inspection here
Is dev.mm-dev.agency secure and safe to use?
We at Idyllum Labs wanted to find out! That is why we built this automated website security scanner and generated this report.
Please understand, that is an automated and unbiased OWASP ZAP based website security scan for dev.mm-dev.agency and has nothing to do with human subjectivity, thoughts, opinions or relationships.
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!
Want to scan and monitor multiple sites at once?Create an account