CVE-2015-9484

Accio | Responsive Onepage Parallax Agency WordPress Theme <= 1.1.0 - Sensitive Information Disclosure

2015-05-15 00:00
Hugo Santiago dos Santos

Strategic Overview

Status
Patched in 1.1.1
Affected Version
<= 1.1.0
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2015-9484
View all Accio | Responsive Onepage Parallax Agency WordPress Theme vulnerabilities

At a glance

CVE-2015-9484 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the Accio WordPress theme, affecting versions <= 1.1.0. 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.1.1; sites on affected versions should update now. Disclosed May 2015, reported by Hugo Santiago dos Santos.

Vulnerability Overview

The "Accio | Responsive Onepage Parallax Agency WordPress Theme" theme for WordPress is vulnerable to sensitive information disclosure in versions up to, and including, 1.1.1. This makes it possible for remote attackers to obtain sensitive information (such as user_login, user_pass, and user_email values) via a direct request to the wp-content/uploads/tmm_db_migrate/wp_users.dat URI.

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

Reaching this weakness in Accio <= 1.1.0 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 Accio the fix is 1.1.1: builds <= 1.1.0 are affected, anything from 1.1.1 onward is not.

Remediation

Update to version 1.1.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: Accio 1.1.1 closes this, and updating the theme is the step that ends it.

  • Alerts

External References

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