Dewplayer <= 1.2 and Advanced Dewplayer < 1.5 - Content Spoofing/Injection
Strategic Overview
- Status
- Patched in 1.5
- Affected Plugin
- Advanced Dewplayer
- Affected Version
< 1.5- CVSS
- 8.6High
- Weakness type
- CWE-74 · Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
- CVE
CVE pending
At a glance
This record tracks a high-severity Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection') vulnerability in the Advanced Dewplayer WordPress plugin, affecting versions < 1.5. It carries a CVSS score of 8.6 (reachable over the network; low attack complexity; high integrity impact). Exploitation requires no authentication. The issue is fixed in version 1.5; sites on affected versions should update now. Disclosed December 2013, reported by Eugene Dokukin.
Vulnerability Overview
The Dewplayer plugin <= 1.2 and Advanced Dewplayer plugin < 1.5 for WordPress are vulnerable to Content Spoofing/Injection. This is due to lack of sanitization of the 'mp3', 'file', 'sound', and 'son' parameters in the dewplayer.swf file. This makes it possible for unauthenticated attackers to inject malicious content into legitimate content 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, and no interaction from a victim user. A successful exploit has high impact on integrity.
CWE-74: Improper Neutralization of Special Elements in Output Used by a Downstream Component ('Injection')
The product constructs all or part of a command, data structure, or record using externally-influenced input from an upstream component, but it does not neutralize or incorrectly neutralizes special elements that could modify how it is parsed or interpreted when it is sent to a downstream component.
Remediation
Update to version 1.5, or a newer patched version
How does WordSec protect against this?
The attempt arrives as an ordinary request to Advanced Dewplayer: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Advanced Dewplayer 1.5 closes this, and updating the plugin is the step that ends it.
- Firewall
- Alerts
External References
Related records
Other vulnerabilities in Advanced Dewplayer
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C