CVE-2012-6499

Age Verification <= 0.4 - Open Redirect

2012-01-10 00:00
Gianluca Brindisi

Strategic Overview

Status
Patched in 0.5
Affected Plugin
Age Verification
Affected Version
<= 0.4
CVSS
6.1Medium
Weakness type
CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE
CVE-2012-6499
View all Age Verification vulnerabilities

At a glance

CVE-2012-6499 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the Age Verification WordPress plugin, affecting versions <= 0.4. It carries a CVSS score of 6.1 (reachable over the network; low attack complexity). Exploitation requires no authentication. The issue is fixed in version 0.5; sites on affected versions should update now. Disclosed January 2012, reported by Gianluca Brindisi.

Vulnerability Overview

Open redirect vulnerability in age-verification.php in the Age Verification plugin 0.4 and earlier for WordPress allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the redirect_to parameter.

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')

Reaching this weakness in Age Verification <= 0.4 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. For Age Verification the fix is 0.5: builds <= 0.4 are affected, anything from 0.5 onward is not.

Remediation

Update to version 0.5, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to Age Verification: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: Age Verification 0.5 closes this, and updating the plugin is the step that ends it.

  • Firewall
  • Alerts

External References

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