WordPress RokBox <= 2.13 - Content Spoofing
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WordPress RokBox
- Affected Version
<= 2.13- CVSS
- 9.1Critical
- Weakness type
- CWE-20 · Improper Input Validation
- CVE
CVE pending
At a glance
This record tracks a critical-severity Improper Input Validation vulnerability in the WordPress RokBox WordPress plugin, affecting versions <= 2.13. It carries a CVSS score of 9.1 (reachable over the network; low attack complexity; high integrity, availability impact). Exploitation requires no authentication. No fixed release has been reported yet; treat installations running this software as exposed. Disclosed December 2012, reported by Eugene Dokukin.
Vulnerability Overview
The WordPress RokBox plugin is vulnerable to Content Spoofing via the 'file', 'config', and 'abouttext' parameters in the 'thumb.php' and 'jwplayer.swf' files in versions up to, and including, 2.13. This makes it possible for unauthenticated attackers to spoof files from other domains.
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, availability.
CWE-20: Improper Input Validation
WordPress RokBox <= 2.13 carries this weakness at file, 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 WordPress RokBox yet, so installs running <= 2.13 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 WordPress RokBox: 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
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C