CVE-2012-10016

Simple Download Button Shortcode <= 1.0 - Information Disclosure via Arbitrary File Downloads

2012-09-17 00:00
Anonymous

Strategic Overview

Status
Patched in 1.1
Affected Version
1.0
CVSS
7.5High
Weakness type
CWE-200 · Exposure of Sensitive Information to an Unauthorized Actor
CVE
CVE-2012-10016
View all simple-download-button-shortcode vulnerabilities

At a glance

CVE-2012-10016 is a high-severity Exposure of Sensitive Information to an Unauthorized Actor vulnerability in the simple-download-button-shortcode WordPress plugin, affecting versions 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; sites on affected versions should update now. Disclosed September 2012.

Vulnerability Overview

The Simple Download Button Shortcode plugin for WordPress is vulnerable to Arbitrary File Downloads in version 1.0. This is due to the plugin not properly validating the path of the file to be downloaded. This makes it possible for unauthenticated attackers to download arbitrary files that may contain sensitive data.

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 simple-download-button-shortcode 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 simple-download-button-shortcode the fix is 1.1: builds 1.0 are affected, anything from 1.1 onward is not.

Remediation

Update to version 1.1, or a newer patched version

How does WordSec protect against this?

The fix is the thing that ends this: simple-download-button-shortcode 1.1 closes this, and updating the plugin is the step that ends it.

  • Alerts

External References

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