HIGH

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

bypass security ·

"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.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

"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.

information disclosure ·

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.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

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.

An attacker could add this website as an invisible layer on top of theirs or impersonate your site by showing selected parts of it in their website

clickjacking · tricking users ·

This vulnerability may allow an attack that is known as clickjacking. Clickjacking is technique where the user thinks they are performing an action, such a clicking a link, on one site. However, in reality their click is actually used to perform some other action on a site they are logged in from the same web browser. This particular vulnerability may allow an attacker to add your site as an invisible layer over their own website. To the user it looks like they are just browsing a harmless website when in reality all their clicks are actually registered on another logged in website.

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

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

In 2010 and 2011 both Twitter and Facebook were vulnerable to a type of clickjacking attack that posted a malicious url to the users Twitter and Facebook account respectively. Friends and followers who clicked on those malicious links were subjected to the same attack. As a result, the attack spread quickly through the social media giants' user bases.

impersonate users ·

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.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Because of this your stored user preferences could leak to other websites and vice versa.

bypass security · information leak · forgery · CSRF ·

Same-site cookies allow servers to mitigate the risk of CSRF and information leakage attacks by asserting that a particular cookie should only be sent with requests initiated from the same registrable domain.

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.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Because of this customers accessing your site from insecure or public networks can lose their login details.

bypass security · impersonate users · eavesdropping ·

If your important site cookies are transmitted unencrypted, someone could steal them. By stealing an unencrypted session cookie an attacker could just log in as the user. This could easily happen in public WiFi networks.

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

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Eavesdropping is the act of secretly or stealthily listening to the private conversation or communications of others without their consent. This type of network attack is generally one of the most effective ones.

Warnings:1:1: The block-all-mixed-content directive is an experimental directive that will be likely added to the CSP specification.1:50: The upgrade-insecure-requests directive is an experimental directive that will be likely added to the CSP specification.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

By ignoring this, an attacker could completely take over your site.

XSS · site takeover · data theft · malware spreading ·

Content Security Policy (CSP) is an extra layer of security that helps to relieve some types of serious attacks, including Cross Site Scripting (XSS) and data injection. These attacks can range from data theft and distribution of malware to total site takeover.

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

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

In 2017, cybercriminals were able to use listings of dental tools on eBay to extract login credentials from their victims. This was achieved by exploiting a XSS vulnerability.

Because of this your users on public computers could press the back button and view secure pages even after logging out.

bypass security ·

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

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Because of this users could upload potentially harmful code to your website. This is especially dangerous in sites where users can upload anything.

phishing · unauthorized hotlinking ·

The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the file types advertised in the Content-Type headers should not be changed and be followed. This allows to opt-out of MIME type sniffing, or, in other words, it is a way to say that the webmasters knew what they were doing.

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.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Cookies can be scoped by domain or path. This check is only concerned with domain scope.The domain scope applied to a cookie determines which domains can access it. For example, a cookie can be scoped strictly to a subdomain e.g. www.nottrusted.com, or loosely scoped to a parent domain e.g. nottrusted.com. In the latter case, any subdomain of nottrusted.com can access the cookie. Loosely scoped cookies are common in mega-applications like google.com and live.com. Cookies set from a subdomain like app.foo.bar are transmitted only to that domain by the browser. However, cookies scoped to a parent-level domain may be transmitted to the parent, or any subdomain of the parent.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.

Because of this some essential parts of the sites code come from third-parties and are therefore not fully under the administrators control. If these sources get hacked or change their behavior you and your customers are at risk.

information leak · forgery · information theft ·

For example, your third-party code provider may suddenly decide they want to collect data from end-users of their script, and this data might include cookies, and HTML5 storage data. By including the script on their domain you are allowing them to make these changes without agreement from you.

The page includes one or more script files from a third-party domain.

This sensitive data is available only for logged in customers. To see detailed security information please create a free account and log in.