In WordPress before 4.7.5, there is improper handling of post meta data values in the XML-RPC API.

According to its self-reported version number, the detected WordPress application is affected by multiple vulnerabilities :

 - A DOM-based cross-site scripting (XSS) vulnerability exists in the uploadSizeError() function within file wp-includes/js/plupload/handlers.js when handling overly large file uploads due to improper validation of user-supplied input to file names before returning it in error messages. An unauthenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2017-9061)

 - A flaw exists in the set_custom_fields() function within file wp-includes/class-wp-xmlrpc-server.php when accessing post meta data due to improper validation of user-supplied input. An authenticated, remote attacker can exploit this to gain unauthorized access to meta data. (CVE-2017-9062)

 - A stored cross-site scripting (XSS) vulnerability exists within file wp-admin/customize.php script due to improper validation of user-supplied input to the blog name before returning it to users. An authenticated, remote attacker can exploit this, via a specially crafted request, to execute arbitrary script code in a user's browser session. (CVE-2017-9063)

 - A cross-site request forgery (XSRF) vulnerability exists in the request_filesystem_credentials() function within file /wp-admin/includes/file.php due to a failure to require multiple steps, explicit confirmation, or a unique token when performing certain sensitive actions. An unauthenticated, remote attacker can exploit this, by convincing a user to follow a specially crafted link, to disclose the user credentials. (CVE-2017-9064)

 - A flaw exists in the XML-RPC API, specifically within file wp-includes/class-wp-xmlrpc-server.php in the _insert_post() function, when handling post meta data due to a lack of capability checks. An unauthenticated, remote attacker can exploit this to manipulate posts without having the required capabilities. (CVE-2017-9065)

 - An flaw exists in the WP_Http::request() function within file wp-includes/class-http.php due to improper validation of user-supplied iput. An unauthenticated, remote attacker can exploit this to redirect the user to a URL of the attacker's choosing. (CVE-2017-9066)

Note that the scanner has not tested for these issues but has instead relied only on the application's self-reported version number.

Several vulnerabilities were discovered in wordpress, a web blogging tool. The Common Vulnerabilities and Exposures project identifies the following issues.

CVE-2017-8295

Potential unauthorized password reset vulnerability. More information are available at :

https://exploitbox.io/vuln/WordPress-Exploit-4-7-Unauth-Password-Reset
-0day-CVE-2017-8295.html

CVE-2017-9061

A cross-site scripting (XSS) vulnerability exists when someone attempts to upload very large files.

CVE-2017-9062

Improper handling of post meta data values in the XML-RPC API.

CVE-2017-9063

Cross-site scripting (XSS) vulnerability in the customizer.

CVE-2017-9064

A Cross Site Request Forgery (CSRF) vulnerability exists in the filesystem credentials dialog.

CVE-2017-9065

Lack of capability checks for post meta data in the XML-RPC API.

For Debian 7 'Wheezy', these problems have been fixed in version 3.6.1+dfsg-1~deb7u15.

We recommend that you upgrade your wordpress packages.

NOTE: Tenable Network Security has extracted the preceding description block directly from the DLA security advisory. Tenable has attempted to automatically clean and format it as much as possible without introducing additional issues.

Several vulnerabilities were discovered in wordpress, a web blogging tool. They would allow remote attackers to force password resets, and perform various cross-site scripting and cross-site request forgery attacks.

Versions of WordPress prior to 4.7.5 are affected by multiple vulnerabilities :

 - A flaw exists that allows a DOM-based cross-site scripting (XSS) attack. This flaw exists exists because the 'uploadSizeError()' function in 'wp-includes/js/plupload/handlers.js' does not validate input to file names before returning it to users in error exists messages for overly large file uploads. This may allow a context-dependent attacker to create a specially crafted request that will execute arbitrary script code in a user's browser session within the trust relationship between their browser and the server. (CVE-2017-9061)
 - A flaw exists in the 'set_custom_fields()' function in 'wp-includes/class-wp-xmlrpc-server.php' that is triggered as certain input is not properly validated when accessing post meta data. This may allow an authenticated, remote attacker to gain unauthorized access to meta data. (CVE-2017-9062)
 - A flaw exists that allows a stored XSS attack. This flaw exists exists because the 'wp-admin/customize.php' script does not validate input to the blog name before returning it to users. This may allow an authenticated, remote attacker to create a specially crafted request that will execute arbitrary script code in a user's browser session within the trust relationship between their browser and the server. (CVE-2017-9063)
 - An unspecified flaw exists in the '_insert_post()' function in 'wp-includes/class-wp-xmlrpc-server.php' that is triggered when handling post meta data. This may allow an attacker to have an unspecified impact. (CVE-2017-9065)
 - An unspecified flaw exists in the 'WP_Http::request()' function in 'wp-includes/class-http.php'. This may allow an attacker to trigger a redirect to an unsafe URL. (CVE-2017-9066)

According to its self-reported version number, the WordPress application running on the remote web server is prior to 4.7.5.
It is, therefore, affected by multiple vulnerabilities :

  - A DOM-based cross-site scripting (XSS) vulnerability     exists in the uploadSizeError() function within file     wp-includes/js/plupload/handlers.js when handling overly     large file uploads due to improper validation of     user-supplied input to file names before returning it in     error messages. An unauthenticated, remote attacker can     exploit this, via a specially crafted request, to     execute arbitrary script code in a user's browser     session. (CVE-2017-9061)

  - A flaw exists in the set_custom_fields() function within     file wp-includes/class-wp-xmlrpc-server.php when     accessing post meta data due to improper validation of     user-supplied input. An authenticated, remote attacker     can exploit this to gain unauthorized access to meta     data. (CVE-2017-9062)

  - A stored cross-site scripting (XSS) vulnerability exists     within file wp-admin/customize.php script due to     improper validation of user-supplied input to the blog     name before returning it to users. An authenticated,     remote attacker can exploit this, via a specially     crafted request, to execute arbitrary script code in a     user's browser session. (CVE-2017-9063)

  - A cross-site request forgery (XSRF) vulnerability exists     in the request_filesystem_credentials() function within     file /wp-admin/includes/file.php due to a failure to     require multiple steps, explicit confirmation, or a     unique token when performing certain sensitive actions.
    An unauthenticated, remote attacker can exploit this,     by convincing a user to follow a specially crafted link,     to disclose the user credentials. (CVE-2017-9064)

  - A flaw exists in the XML-RPC API, specifically within     file wp-includes/class-wp-xmlrpc-server.php in the
    _insert_post() function, when handling post meta data     due to a lack of capability checks. An unauthenticated,     remote attacker can exploit this to manipulate posts     without having the required capabilities.
    (CVE-2017-9065)

  - A flaw exists in the WP_Http::request() function within     file wp-includes/class-http.php due to improper     validation of user-supplied iput. An unauthenticated,     remote attacker can exploit this to redirect the user to     a URL of the attacker's choosing. (CVE-2017-9066)

Note that Nessus has not tested for these issues but has instead relied only on the application's self-reported version number.

ID	Name	Product	Family	Severity
98293	WordPress 3.7.x < 3.7.21 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98292	WordPress 3.8.x < 3.8.21 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98291	WordPress 3.9.x < 3.9.19 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98290	WordPress 4.0.x < 4.0.18 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98289	WordPress 4.1.x < 4.1.18 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98288	WordPress 4.2.x < 4.2.15 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98287	WordPress 4.3.x < 4.3.11 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98286	WordPress 4.4.x < 4.4.10 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98285	WordPress 4.5.x < 4.5.9 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98284	WordPress 4.6.x < 4.6.6 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
98283	WordPress 4.7.x < 4.7.5 Multiple Vulnerabilities	Web App Scanning	Component Vulnerability	high
100602	Debian DLA-975-1 : wordpress security update	Nessus	Debian Local Security Checks	high
100561	Debian DSA-3870-1 : wordpress - security update	Nessus	Debian Local Security Checks	high
700121	WordPress < 4.7.5 Multiple Vulnerabilities	Nessus Network Monitor	CGI	high
100298	WordPress < 4.7.5 Multiple Vulnerabilities	Nessus	CGI abuses	high

Detections

Analytics

CVE-2017-9062

high

Tenable Plugins

high

high

high

high

high

high

high

high

high

high

high

high

high

high

high