CVE-2017-14721

WordPress Core < 4.8.2 - Stored Cross-Site Scripting via Plugin Names

2017-09-19 00:00

Strategic Overview

Status: Patched in 3.7.22
Affected Core: WordPress 4.8
Affected Version: 3.7 – 4.8.1 · 13 branches
CVSS: 5.5Medium
Weakness type: CWE-79 · Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')
CVE: CVE-2017-14721

At a glance

CVE-2017-14721 is a medium-severity Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting') vulnerability in the WordPress 4.8 WordPress release line, affecting 3.7 – 4.8.1 · 13 branches. It carries a CVSS score of 5.5 (reachable over the network; low attack complexity). The issue is fixed in version 3.7.22; sites on affected versions should update now. Disclosed September 2017, reported by 陈瑞琦 (Chen Ruiqi).

Vulnerability Overview

Before version 4.8.2, WordPress allowed Cross-Site scripting in the plugin editor via a crafted plugin name.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, with low attack complexity — no special timing or configuration is needed, and no interaction from a victim user.

CWE-79: Improper Neutralization of Input During Web Page Generation ('Cross-site Scripting')

Reaching this weakness in WordPress 4.8 3.7 – 4.8.1 · 13 branches takes a caller who can reach the endpoint. Cross-site scripting happens when input from a request is written into a page without being escaped for the context it lands in, so the browser parses attacker-supplied text as markup or script.

Injected script runs with the privileges of whoever views the affected page, which is how these flaws turn into administrator session theft, silent account creation or persistent backdoors in page content. For WordPress 4.8 the fix is 3.7.22: builds 3.7 – 4.8.1 · 13 branches are affected, anything from 3.7.22 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.22, 3.8.22, 3.9.20, 4.0.19, 4.1.19, 4.2.16, 4.3.12, 4.4.11, 4.5.10, 4.6.7, 4.7.6, 4.8.2

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 4.8: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 3.7.22 is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2017-14721 https://www.wordfence.com/threat-intel/vulnerabilities/id/2dccdaa8-5095-42c4-9ca8-90fb444c0ae4 https://nvd.nist.gov/vuln/detail/CVE-2017-14721

Related records

Same weakness class

Other vulnerabilities in WordPress 4.8

CVSS Vector

5.5

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredHigh
User InteractionNone
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/