ZAP Scanning Report

Summary of Alerts

Risk Level

Number of Alerts

High

2

Medium

1

Low

5

Informational

0

Alert Detail

High (Medium)

Path Traversal

Description

The Path Traversal attack technique allows an attacker access to files, directories, and commands that potentially reside outside the web document root directory. An attacker may manipulate a URL in such a way that the web site will execute or reveal the contents of arbitrary files anywhere on the web server. Any device that exposes an HTTP-based interface is potentially vulnerable to Path Traversal.

Most web sites restrict user access to a specific portion of the file-system, typically called the "web document root" or "CGI root" directory. These directories contain the files intended for user access and the executable necessary to drive web application functionality. To access files or execute commands anywhere on the file-system, Path Traversal attacks will utilize the ability of special-characters sequences.

The most basic Path Traversal attack uses the "../" special-character sequence to alter the resource location requested in the URL. Although most popular web servers will prevent this technique from escaping the web document root, alternate encodings of the "../" sequence may help bypass the security filters. These method variations include valid and invalid Unicode-encoding ("..%u2216" or "..%c0%af") of the forward slash character, backslash characters ("..\") on Windows-based servers, URL encoded characters "%2e%2e%2f"), and double URL encoding ("..%255c") of the backslash character.

Even if the web server properly restricts Path Traversal attempts in the URL path, a web application itself may still be vulnerable due to improper handling of user-supplied input. This is a common problem of web applications that use template mechanisms or load static text from files. In variations of the attack, the original URL parameter value is substituted with the file name of one of the web application's dynamic scripts. Consequently, the results can reveal source code because the file is interpreted as text instead of an executable script. These techniques often employ additional special characters such as the dot (".") to reveal the listing of the current working directory, or "%00" NULL characters in order to bypass rudimentary file extension checks.

URL

http://www.website.web/contact?query=c%3A%2F

Method

GET

Parameter

query

Attack

c:/

Evidence

etc

URL

http://www.website.web/faq/?query=c%3A%2F

Method

GET

Parameter

query

Attack

c:/

Evidence

etc

URL

http://www.website.web/faq?query=c%3A%2F

Method

GET

Parameter

query

Attack

c:/

Evidence

etc

URL

http://www.website.web/contact/?query=c%3A%2F

Method

GET

Parameter

query

Attack

c:/

Evidence

etc

URL

http://www.website.web/wp-comments-post.php

Method

POST

Parameter

comment

Attack

wp-comments-post.php

Instances

5

Solution

Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as "red" or "blue."

For filenames, use stringent whitelists that limit the character set to be used. If feasible, only allow a single "." character in the filename to avoid weaknesses, and exclude directory separators such as "/". Use a whitelist of allowable file extensions.

Warning: if you attempt to cleanse your data, then do so that the end result is not in the form that can be dangerous. A sanitizing mechanism can remove characters such as '.' and ';' which may be required for some exploits. An attacker can try to fool the sanitizing mechanism into "cleaning" data into a dangerous form. Suppose the attacker injects a '.' inside a filename (e.g. "sensi.tiveFile") and the sanitizing mechanism removes the character resulting in the valid filename, "sensitiveFile". If the input data are now assumed to be safe, then the file may be compromised.

Inputs should be decoded and canonicalized to the application's current internal representation before being validated. Make sure that your application does not decode the same input twice. Such errors could be used to bypass whitelist schemes by introducing dangerous inputs after they have been checked.

Use a built-in path canonicalization function (such as realpath() in C) that produces the canonical version of the pathname, which effectively removes ".." sequences and symbolic links.

Run your code using the lowest privileges that are required to accomplish the necessary tasks. If possible, create isolated accounts with limited privileges that are only used for a single task. That way, a successful attack will not immediately give the attacker access to the rest of the software or its environment. For example, database applications rarely need to run as the database administrator, especially in day-to-day operations.

When the set of acceptable objects, such as filenames or URLs, is limited or known, create a mapping from a set of fixed input values (such as numeric IDs) to the actual filenames or URLs, and reject all other inputs.

Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by your software.

OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows you to specify restrictions on file operations.

This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.

Reference

http://projects.webappsec.org/Path-Traversal

http://cwe.mitre.org/data/definitions/22.html

CWE Id

22

WASC Id

33

Source ID

1

High (Medium)

Remote OS Command Injection

Description

Attack technique used for unauthorized execution of operating system commands. This attack is possible when an application accepts untrusted input to build operating system commands in an insecure manner involving improper data sanitization, and/or improper calling of external programs.

URL

http://www.website.web/feed/?query=query%22%26timeout+%2FT+15%26%22

Method

GET

Parameter

query

Attack

query"&timeout /T 15&"

URL

http://www.website.web/xmlrpc.php?query=query%3Bsleep+%7B0%7D%3B

Method

GET

Parameter

query

Attack

query;sleep {0};

URL

http://www.website.web/wp-login.php?reauth=1%3Bstart-sleep+-s+15&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

reauth

Attack

1;start-sleep -s 15

URL

http://www.website.web/wp-content/plugins/beaver-builder-lite-version/js/jquery.easing.min.js?ver=1.4%3Bstart-sleep+-s+%7B0%7D

Method

GET

Parameter

ver

Attack

1.4;start-sleep -s {0}

Instances

4

Solution

If at all possible, use library calls rather than external processes to recreate the desired functionality.

Run your code in a "jail" or similar sandbox environment that enforces strict boundaries between the process and the operating system. This may effectively restrict which files can be accessed in a particular directory or which commands can be executed by your software.

OS-level examples include the Unix chroot jail, AppArmor, and SELinux. In general, managed code may provide some protection. For example, java.io.FilePermission in the Java SecurityManager allows you to specify restrictions on file operations.

This may not be a feasible solution, and it only limits the impact to the operating system; the rest of your application may still be subject to compromise.

For any data that will be used to generate a command to be executed, keep as much of that data out of external control as possible. For example, in web applications, this may require storing the command locally in the session's state instead of sending it out to the client in a hidden form field.

Use 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, consider using the ESAPI Encoding control or a similar tool, library, or framework. These will help the programmer encode outputs in a manner less prone to error.

If you need to use dynamically-generated query strings or commands in spite of the risk, properly quote arguments and escape any special characters within those arguments. The most conservative approach is to escape or filter all characters that do not pass an extremely strict whitelist (such as everything that is not alphanumeric or white space). If some special characters are still needed, such as white space, wrap each argument in quotes after the escaping/filtering step. Be careful of argument injection.

If the program to be executed allows arguments to be specified within an input file or from standard input, then consider using that mode to pass arguments instead of the command line.

If available, use structured mechanisms that automatically enforce the separation between data and code. These mechanisms may be able to provide the relevant quoting, encoding, and validation automatically, instead of relying on the developer to provide this capability at every point where output is generated.

Some languages offer multiple functions that can be used to invoke commands. Where possible, identify any function that invokes a command shell using a single string, and replace it with a function that requires individual arguments. These functions typically perform appropriate quoting and filtering of arguments. For example, in C, the system() function accepts a string that contains the entire command to be executed, whereas execl(), execve(), and others require an array of strings, one for each argument. In Windows, CreateProcess() only accepts one command at a time. In Perl, if system() is provided with an array of arguments, then it will quote each of the arguments.

Assume all input is malicious. Use an "accept known good" input validation strategy, i.e., use a whitelist of acceptable inputs that strictly conform to specifications. Reject any input that does not strictly conform to specifications, or transform it into something that does. Do not rely exclusively on looking for malicious or malformed inputs (i.e., do not rely on a blacklist). However, blacklists can be useful for detecting potential attacks or determining which inputs are so malformed that they should be rejected outright.

When performing input validation, consider all potentially relevant properties, including length, type of input, the full range of acceptable values, missing or extra inputs, syntax, consistency across related fields, and conformance to business rules. As an example of business rule logic, "boat" may be syntactically valid because it only contains alphanumeric characters, but it is not valid if you are expecting colors such as "red" or "blue."

When constructing OS command strings, use stringent whitelists that limit the character set based on the expected value of the parameter in the request. This will indirectly limit the scope of an attack, but this technique is less important than proper output encoding and escaping.

Note that proper output encoding, escaping, and quoting is the most effective solution for preventing OS command injection, although input validation may provide some defense-in-depth. This is because it effectively limits what will appear in output. Input validation will not always prevent OS command injection, especially if you are required to support free-form text fields that could contain arbitrary characters. For example, when invoking a mail program, you might need to allow the subject field to contain otherwise-dangerous inputs like ";" and ">" characters, which would need to be escaped or otherwise handled. In this case, stripping the character might reduce the risk of OS command injection, but it would produce incorrect behavior because the subject field would not be recorded as the user intended. This might seem to be a minor inconvenience, but it could be more important when the program relies on well-structured subject lines in order to pass messages to other components.

Even if you make a mistake in your validation (such as forgetting one out of 100 input fields), appropriate encoding is still likely to protect you from injection-based attacks. As long as it is not done in isolation, input validation is still a useful technique, since it may significantly reduce your attack surface, allow you to detect some attacks, and provide other security benefits that proper encoding does not address.

Reference

http://cwe.mitre.org/data/definitions/78.html

https://www.owasp.org/index.php/Command_Injection

CWE Id

78

WASC Id

31

Source ID

1

Medium (Medium)

X-Frame-Options Header Not Set

Description

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

URL

http://www.website.web/contact/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/wp-comments-post.php

Method

POST

Parameter

X-Frame-Options

URL

http://www.website.web/contact/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/faq/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/blog/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/portfolio/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/hello-world/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/faq/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/about/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/portfolio/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/hello-world/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/?s

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/about/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/gallery/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/2018/10/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/services/embed/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/author/admin/

Method

GET

Parameter

X-Frame-Options

URL

http://www.website.web/gallery/

Method

GET

Parameter

X-Frame-Options

Instances

21

Solution

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

Reference

http://blogs.msdn.com/b/ieinternals/archive/2010/03/30/combating-clickjacking-with-x-frame-options.aspx

CWE Id

16

WASC Id

15

Source ID

3

Low (Medium)

Cross-Domain JavaScript Source File Inclusion

Description

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

URL

http://www.website.web/about/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/2018/10/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/faq/embed/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/?s

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/services/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/gallery/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/contact/embed/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/author/admin/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/hello-world/embed/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/faq/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-comments-post.php

Method

POST

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-login.php

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-login.php

Method

POST

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/contact/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

POST

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/portfolio/embed/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/blog/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

URL

http://www.website.web/gallery/embed/

Method

GET

Parameter

https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js

Evidence

<script src='https://img1.wsimg.com/tcc/tcc_l.combined.1.0.6.min.js'></script>

Instances

26

Solution

Ensure JavaScript source files are loaded from only trusted sources, and the sources can't be controlled by end users of the application.

Reference

CWE Id

829

WASC Id

15

Source ID

3

Low (Medium)

X-Content-Type-Options Header Missing

Description

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.

URL

http://www.website.web/wp-content/uploads/2018/10/portfolio-1b.jpg

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/bb-plugin/cache/19-layout-partial.css?ver=28c1f1d7033c651ae8bd93a89f929201

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/2018/10/home-1.jpg

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/bb-plugin/cache/156-layout-partial.js?ver=28c1f1d7033c651ae8bd93a89f929201

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/services/embed/

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/robots.txt

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/plugins/contact-form-7/includes/js/scripts.js?ver=5.0.4

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-includes/js/wp-embed.min.js?ver=4.9.8

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/themes/twentyseventeen/assets/js/html5.js?ver=3.7.3

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/plugins/beaver-builder-lite-version/js/jquery.easing.min.js?ver=1.4

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/bb-plugin/cache/156-layout.css?ver=28c1f1d7033c651ae8bd93a89f929201

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-admin/images/w-logo-blue.png

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/bb-plugin/cache/162-layout-partial.css?ver=28c1f1d7033c651ae8bd93a89f929201

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/portfolio/

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/themes/twentyseventeen/assets/js/skip-link-focus-fix.js?ver=1.0

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/hello-world/

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/2018/10/portfolio-2b.jpg

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/plugins/beaver-builder-lite-version/css/jquery.magnificpopup.css?ver=2.1.4.5

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-content/uploads/bb-plugin/cache/162-layout.css?ver=28c1f1d7033c651ae8bd93a89f929201

Method

GET

Parameter

X-Content-Type-Options

URL

http://www.website.web/wp-includes/js/backbone.min.js?ver=1.2.3

Method

GET

Parameter

X-Content-Type-Options

Instances

110

Solution

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.

Other information

This issue still applies to error type pages (401, 403, 500, etc) as those pages are often still affected by injection issues, in which case there is still concern for browsers sniffing pages away from their actual content type.

At "High" threshold this scanner will not alert on client or server error responses.

Reference

http://msdn.microsoft.com/en-us/library/ie/gg622941%28v=vs.85%29.aspx

https://www.owasp.org/index.php/List_of_useful_HTTP_headers

CWE Id

16

WASC Id

15

Source ID

3

Low (Medium)

Cookie No HttpOnly Flag

Description

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.

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpress_logged_in_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wordpress_logged_in_3ab696ed422187d39dc012fbde238174

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

GET

Parameter

wordpress_test_cookie

Evidence

Set-Cookie: wordpress_test_cookie

URL

http://www.website.web/wp-login.php

Method

GET

Parameter

wordpress_test_cookie

Evidence

Set-Cookie: wordpress_test_cookie

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpressuser_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wordpressuser_3ab696ed422187d39dc012fbde238174

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpress_test_cookie

Evidence

Set-Cookie: wordpress_test_cookie

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

POST

Parameter

wordpress_test_cookie

Evidence

Set-Cookie: wordpress_test_cookie

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpresspass_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wordpresspass_3ab696ed422187d39dc012fbde238174

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpress_sec_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wordpress_sec_3ab696ed422187d39dc012fbde238174

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wordpress_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wordpress_3ab696ed422187d39dc012fbde238174

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wp-settings-0

Evidence

Set-Cookie: wp-settings-0

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wp-settings-time-0

Evidence

Set-Cookie: wp-settings-time-0

URL

http://www.website.web/wp-login.php

Method

POST

Parameter

wordpress_test_cookie

Evidence

Set-Cookie: wordpress_test_cookie

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

wp-postpass_3ab696ed422187d39dc012fbde238174

Evidence

Set-Cookie: wp-postpass_3ab696ed422187d39dc012fbde238174

Instances

13

Solution

Ensure that the HttpOnly flag is set for all cookies.

Reference

http://www.owasp.org/index.php/HttpOnly

CWE Id

16

WASC Id

13

Source ID

3

Low (Medium)

Web Browser XSS Protection Not Enabled

Description

Web Browser XSS Protection is not enabled, or is disabled by the configuration of the 'X-XSS-Protection' HTTP response header on the web server

URL

http://www.website.web/wp-content/uploads/2018/10/gallery-5-1024x683.jpg

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-content/uploads/2018/10/gallery-4-683x1024.jpg

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-comments-post.php

Method

POST

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/contact/embed/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/contact/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-login.php?action=lostpassword

Method

POST

Parameter

X-XSS-Protection

URL

http://www.website.web/faq/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-admin/admin-ajax.php

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/faq/embed/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/blog/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-content/uploads/2018/10/gallery-6-1024x683.jpg

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/2018/10/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/hello-world/embed/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/wp-content/uploads/2018/10/gallery-6-1060x550.jpg

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/about/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/portfolio/

Method

GET

Parameter

X-XSS-Protection

URL

http://www.website.web/?s

Method

GET

Parameter

X-XSS-Protection

Instances

36

Solution

Ensure that the web browser's XSS filter is enabled, by setting the X-XSS-Protection HTTP response header to '1'.

Other information

The X-XSS-Protection HTTP response header allows the web server to enable or disable the web browser's XSS protection mechanism. The following values would attempt to enable it:

X-XSS-Protection: 1; mode=block

X-XSS-Protection: 1; report=http://www.example.com/xss

The following values would disable it:

X-XSS-Protection: 0

The X-XSS-Protection HTTP response header is currently supported on Internet Explorer, Chrome and Safari (WebKit).

Note that this alert is only raised if the response body could potentially contain an XSS payload (with a text-based content type, with a non-zero length).

Reference

https://www.owasp.org/index.php/XSS_(Cross_Site_Scripting)_Prevention_Cheat_Sheet

https://blog.veracode.com/2014/03/guidelines-for-setting-security-headers/

CWE Id

933

WASC Id

14

Source ID

3

Low (Medium)

Password Autocomplete in Browser

Description

The AUTOCOMPLETE attribute is not disabled on an HTML FORM/INPUT element containing password type input. Passwords may be stored in browsers and retrieved.

URL

http://www.website.web/wp-login.php

Method

POST

Parameter

user_pass

Evidence

<input type="password" name="pwd" id="user_pass" aria-describedby="login_error" class="input" value="" size="20" />

URL

http://www.website.web/wp-login.php

Method

GET

Parameter

user_pass

Evidence

<input type="password" name="pwd" id="user_pass" aria-describedby="login_error" class="input" value="" size="20" />

URL

http://www.website.web/wp-login.php?reauth=1&redirect_to=http%3A%2F%2Fwww.website.web%2Fwp-admin%2F

Method

GET

Parameter

user_pass

Evidence

<input type="password" name="pwd" id="user_pass" aria-describedby="login_error" class="input" value="" size="20" />

Instances

3

Solution

Turn off the AUTOCOMPLETE attribute in forms or individual input elements containing password inputs by using AUTOCOMPLETE='OFF'.

Reference

http://www.w3schools.com/tags/att_input_autocomplete.asp

https://msdn.microsoft.com/en-us/library/ms533486%28v=vs.85%29.aspx

CWE Id

525

WASC Id

15

Source ID

3