CVE-2016-9263

WordPress Core < 4.9.1 - Cross-domain Flash injection

2017-10-10 00:00
Anonymous

Strategic Overview

Status
Patched in 3.7.25
Affected Core
WordPress 4.9
Affected Version
3.7 – 4.9.1 · 14 branches
CVSS
4.7Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE-2016-9263
View all WordPress 4.9 vulnerabilities

At a glance

CVE-2016-9263 is a medium-severity Improper Input Validation vulnerability in the WordPress 4.9 WordPress release line, affecting 3.7 – 4.9.1 · 14 branches. It carries a CVSS score of 4.7 (reachable over the network). Exploitation requires no authentication. The issue is fixed in version 3.7.25; sites on affected versions should update now. Disclosed October 2017.

Vulnerability Overview

WordPress through 4.9.1, when domain-based flashmediaelement.swf sandboxing is not used, allows remote attackers to conduct cross-domain Flash injection (XSF) attacks by leveraging code contained within the wp-includes/js/mediaelement/flashmediaelement.swf file.

Technical Analysis

The vector marks this flaw as remotely reachable over the network, and no privileges on the target site.

CWE-20: Improper Input Validation

Reaching this weakness in WordPress 4.9 3.7 – 4.9.1 · 14 branches takes a caller who can reach the endpoint. Improper input validation means the application accepts input without confirming it has the form, type or range the code downstream assumes.

The concrete impact depends on where the unvalidated value lands, which is why records in this class range from cosmetic bugs to full compromise. For WordPress 4.9 the fix is 3.7.25: builds 3.7 – 4.9.1 · 14 branches are affected, anything from 3.7.25 onward is not.

Remediation

Update to one of the following versions, or a newer patched version: 3.7.25, 3.8.25, 3.9.24, 4.0.22, 4.1.22, 4.2.19, 4.3.15, 4.4.14, 4.5.13, 4.6.10, 4.7.9, 4.8.5, 4.9.2

How does WordSec protect against this?

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

  • Firewall
  • Alerts

External References

Related records

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