RokIntroScroller <= 1.8 - Full Path Disclosure

2013-09-19 00:00
Eugene Dokukin

Strategic Overview

Status
Patched in 1.9
Affected Plugin
RokIntroScroller
Affected Version
<= 1.8
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE pending
View all RokIntroScroller vulnerabilities

At a glance

This record tracks a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the RokIntroScroller WordPress plugin, affecting versions <= 1.8. It carries a CVSS score of 7.5 (reachable over the network; low attack complexity; high confidentiality impact). Exploitation requires no authentication. The issue is fixed in version 1.9; sites on affected versions should update now. Disclosed September 2013, reported by Eugene Dokukin.

Vulnerability Overview

The RokIntroScroller plugin for WordPress is vulnerable to Full Path Disclosure via the 'src' parameter in the 'thumb.php' file in versions up to, and including, 1.8. This makes it possible for unauthenticated attackers to read the full path to an arbitrary file within the vulnerable service, the information gathered can potentially be used for subsequent attacks.

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 confidentiality.

CWE-200: Exposure of Sensitive Information to an Unauthorized Actor

RokIntroScroller <= 1.8 carries this weakness at src, and reaching it 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. For RokIntroScroller the fix is 1.9: builds <= 1.8 are affected, anything from 1.9 onward is not.

Remediation

Update to version 1.9, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: RokIntroScroller 1.9 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

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