CVE-2017-14725

WordPress Core < 4.8.2 - Open Redirect in Admin Dashboard

2017-09-19 00:00
Yasin Soliman (ysx)

Strategic Overview

Status
Patched in 3.7.22
Affected Core
WordPress 4.8
Affected Version
3.7 – 4.8.1 · 13 branches
CVSS
3.5Low
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2017-14725
View all WordPress 4.8 vulnerabilities

At a glance

CVE-2017-14725 is a low-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the WordPress 4.8 WordPress release line, affecting 3.7 – 4.8.1 · 13 branches. It carries a CVSS score of 3.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 Yasin Soliman (ysx).

Vulnerability Overview

Before version 4.8.2, WordPress was susceptible to an open redirect attack in wp-admin/edit-tag-form.php and wp-admin/user-edit.php.

Technical Analysis

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

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Reaching this weakness in WordPress 4.8 3.7 – 4.8.1 · 13 branches takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. 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

Related records

Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C