CVE-2013-10024

WordPress Exit Strategy <= 1.55 - Information Exposure

2013-05-28 00:00
Anonymous

Strategic Overview

Status
Patched in 1.59
Affected Version
<= 1.55
CVSS
5.3Medium
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2013-10024
View all WordPress Exit Strategy vulnerabilities

At a glance

CVE-2013-10024 is a medium-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the WordPress Exit Strategy WordPress plugin, affecting versions <= 1.55. It carries a CVSS score of 5.3 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 1.59; sites on affected versions should update now. Disclosed May 2013.

Vulnerability Overview

The WordPress Exit Strategy plugin for WordPress is vulnerable to Full Path Disclosure in all versions up to, and including, 1.55. This is due the plugin not properly restricting direct access to the exitpage.php file. This makes it possible for unauthenticated attackers to retrieve the full path of the web application, which can be used to aid other attacks. The information displayed is not useful on its own, and requires another vulnerability to be present for damage to an affected website.

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 Exit Strategy <= 1.55 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 WordPress Exit Strategy the fix is 1.59: builds <= 1.55 are affected, anything from 1.59 onward is not.

Remediation

Update to version 1.59, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: WordPress Exit Strategy 1.59 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

Related records

Other vulnerabilities in WordPress Exit Strategy

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