DT Chocolate <= 1.0 - Open Redirect

2013-02-03 00:00
Ashiyane Digital Security Team

Strategic Overview

Status
Unpatched
Affected Theme
Chocolate WP – Responsive Photography Theme | Photography
Affected Version
<= 1.0
CVSS
4.7Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE pending
View all Chocolate WP – Responsive Photography Theme | Photography vulnerabilities

At a glance

This record tracks a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Chocolate WP WordPress theme, affecting versions <= 1.0. It carries a CVSS score of 4.7 (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 February 2013, reported by Ashiyane Digital Security Team.

Vulnerability Overview

The DT Chocolate theme for WordPress is vulnerable to Open Redirect in versions up to, and including, 1.0. This is due to a lack of sanitization of user-supplied input via the 'image' parameter. This makes it possible for attackers to redirect users to arbitrary websites.

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.

CWE-601: URL Redirection to Untrusted Site ('Open Redirect')

Chocolate WP <= 1.0 carries this weakness at image, and reaching it takes a caller who can reach the endpoint. An open redirect is a page that takes a destination from the request and sends the browser there without checking that the destination belongs to the site.

A link that starts on a trusted domain finishes on an attacker's, which is what makes phishing and consent-screen abuse credible to the person clicking it. No fixed build of this theme is recorded for Chocolate WP yet, so installs running <= 1.0 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?

The attempt arrives as an ordinary request to Chocolate WP: WordSec's web application firewall inspects request payloads before WordPress loads them. No patched version is recorded yet, which is the case where a filtering layer matters most, because there is nothing to update to.

  • Firewall
  • Alerts

External References

https://www.wordfence.com/threat-intel/vulnerabilities/id/3f937290-fa45-4ce0-84f0-a42c83cd3bdf

Related records

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