CVE-2007-3639

WordPress Core < 2.2.2 - Open Redirect

2007-08-08 00:00

Strategic Overview

Status: Patched in 2.2.2
Affected Core: WordPress 2.2
Affected Version: <= 2.2.1
CVSS: 6.1Medium
Weakness type: CWE-601 · URL Redirection to Untrusted Site ('Open Redirect')
CVE: CVE-2007-3639

At a glance

CVE-2007-3639 is a medium-severity URL Redirection to Untrusted Site ('Open Redirect') vulnerability in the WordPress 2.2 WordPress release line, affecting <= 2.2.1. 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 2.2.2; sites on affected versions should update now. Disclosed August 2007.

Vulnerability Overview

WordPress before 2.2.2 allows remote attackers to redirect visitors to other websites and potentially obtain sensitive information via (1) the _wp_http_referer parameter to wp-pass.php, related to the wp_get_referer function in wp-includes/functions.php; and possibly other vectors related to (2) wp-includes/pluggable.php and (3) the wp_nonce_ays function in wp-includes/functions.php.

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 WordPress 2.2 <= 2.2.1 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 WordPress 2.2 the fix is 2.2.2: builds <= 2.2.1 are affected, anything from 2.2.2 onward is not.

Remediation

Update to version 2.2.2, or a newer patched version

How does WordSec protect against this?

The attempt arrives as an ordinary request to WordPress 2.2: WordSec's web application firewall inspects request payloads before WordPress loads them. None of that substitutes for the fix: updating to 2.2.2 is the step that ends it.

Firewall
Alerts

External References

https://www.cve.org/CVERecord?id=CVE-2007-3639 https://www.wordfence.com/threat-intel/vulnerabilities/id/2822114a-ffc2-43dd-bbf1-e4504aababfb https://nvd.nist.gov/vuln/detail/CVE-2007-3639

Related records

Same weakness class

Other vulnerabilities in WordPress 2.2

CVSS Vector

6.1

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N

Base

Attack VectorNetwork
Attack ComplexityLow
Privileges RequiredNone
User InteractionRequired
ScopeChanged
ConfidentialityLow
IntegrityLow
AvailabilityNone

This record contains material that is subject to copyright

CVE Usage: MITRE hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute Common Vulnerabilities and Exposures (CVE®). Any copy you make for such purposes is authorized provided that you reproduce MITRE's copyright designation and this license in any such copy.

https://www.cve.org/Legal/TermsOfUse

Defiant hereby grants you a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, sublicense, and distribute this software vulnerability information. Any copy of the software vulnerability information you make for such purposes is authorized provided that you include a hyperlink to this vulnerability record and reproduce Defiant's copyright designation and this license in any such copy.

https://www.wordfence.com/wordfence-intelligence-terms-and-conditions/