WordPress RokBox <= 2.13 - Sensitive Data Disclosure
Strategic Overview
- Status
- Unpatched
- Affected Plugin
- WordPress RokBox
- Affected Version
<= 2.13- CVSS
- 5.3Medium
- Weakness type
- CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
- CVE
CVE pending
At a glance
This record tracks a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WordPress RokBox WordPress plugin, affecting versions <= 2.13. It carries a CVSS score of 5.3 (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 2012, reported by Eugene Dokukin.
Vulnerability Overview
The WordPress RokBox plugin is vulnerable to Sensitive Data Exposure in versions up to, and including, 2.13 via the error_log. This can allow unauthenticated attackers to extract sensitive data including error logs which may disclose full paths.
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.
CWE-200: Exposure of Sensitive Information to an Unauthorized Actor
Reaching this weakness in WordPress RokBox <= 2.13 takes a caller who can reach the endpoint. Sensitive information exposure means data the application intended to keep internal is returned to a caller who should not be able to see it.
The disclosed data — credentials, tokens, customer records or internal paths — is usually worth more as material for a follow-up attack than as an end in itself. 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?
No patched version is recorded yet, so there is nothing to update to; WordSec's vulnerability alerts flag this record the moment that changes.
- Alerts
External References
Related records
Same weakness class
Vulnerability data © Defiant, Inc., provided under the Wordfence Intelligence T&C