dbcve.org
WordPressCMS

CVE-2007-1599

MEDIUM · 6.5 CVSS v2.0 Published 2007-03-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
wp-login.php in WordPress allows remote attackers to redirect authenticated users to other websites and potentially obtain sensitive information via the redirect_to parameter.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

wp-login.php in WordPress contains an open redirect vulnerability where the redirect_to parameter is not properly validated, allowing authenticated users to be redirected to external malicious websites. This could facilitate phishing attacks or credential theft by tricking users into visiting attacker-controlled sites that mimic the legitimate WordPress login.

MitigationValidate that the redirect_to parameter contains only relative/internal URLs or matches an allowed whitelist of domains before performing the redirect.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
WordPressCMS
Affected:= 2.1.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Authentication
Single
Confidentiality
Partial
Integrity
Partial
Availability
Partial

AV:N/AC:L/Au:S/C:P/I:P/A:P

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed WordPress version
    Check the version number in/wp-includes/version.php or the meta tag in the HTML source of any WordPress page
    Affected if The installed version is exactly 2.1.2
  2. Verify wp-login.php exists
    Check if wp-login.php file exists in the WordPress root directory
    Affected if The file exists and the WordPress version is 2.1.2
  3. Inspect redirect_to parameter handling
    Open wp-login.php and search for the redirect_to parameter processing - look for code that handles the redirect after login using the redirect_to variable
    Affected if The redirect_to parameter is processed without validation and the version is 2.1.2
  4. Test redirect behavior (if safe to do)
    In a non-production test environment, submit a login request with redirect_to set to an external domain (e.g., redirect_to=http://evil.com) and observe if the browser is redirected there after authentication
    Affected if The login process redirects to the external URL specified in redirect_to

You are affected if the installed WordPress version is exactly 2.1.2 AND the wp-login.php file processes the redirect_to parameter without validating that it points to an internal URL.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Validate that the redirect_to parameter contains only relative/internal URLs or matches an allowed whitelist of domains before performing the redirect.

Fix this in WordPress Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2007-1599 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2007-1599 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data