Flash player widget <= 1.3 - Content Spoofing

2013-12-30 00:00
Henri Salo (fgeek)

Strategic Overview

Status
Unpatched
Affected Plugin
flash-player-widget
Affected Version
*
CVSS
4.7Medium
Weakness type
CWE-20 · Improper Input Validation
CVE
CVE pending
View all flash-player-widget vulnerabilities

At a glance

This record tracks a medium-severity Improper Input Validation vulnerability in the flash-player-widget WordPress plugin, affecting versions *. It carries a CVSS score of 4.7 (reachable over the network; low attack complexity). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2013, reported by Henri Salo (fgeek).

Vulnerability Overview

The Flash player widget plugin for WordPress is vulnerable to Content Spoofing in versions up to, and including, 1.3. This is due to insufficient sanitization of user input on the 'mp3' parameter. This makes it possible for unauthenticated attackers to to inject arbitrary content in pages if they can successfully trick a user into performing an action such as clicking on a link.

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 privileges on the target site.

CWE-20: Improper Input Validation

flash-player-widget * carries this weakness at mp3, and reaching it 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. No fixed build of this plugin is recorded for flash-player-widget yet, so installs running * stay exposed until the vendor ships one.

Remediation

No known patch available. Please review the vulnerability's details in depth and employ mitigations based on your organization's risk tolerance. It may be best to uninstall the affected software and find a replacement.

How does WordSec protect against this?

The attempt arrives as an ordinary request to flash-player-widget: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

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