# CVE-2012-4032: Open redirect in n/a

> Remote attackers can redirect users to malicious sites via the login page, facilitating phishing attacks against WebsitePanel users.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 17 Jul 2012
- **Updated:** 6 Aug 2024
- **Also known as:** GHSA-f4j3-3p4m-g2gh

## What is CVE-2012-4032?

CVE-2012-4032 is a medium-severity vulnerability in n/a, published on 17 Jul 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Open redirect vulnerability in the login page in WebsitePanel before 1.2.2.1 allows remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in ReturnUrl to Default.aspx.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2012-4032?

It affects 1 product.


Products: Websitepanel Websitepanel.

## How do I fix CVE-2012-4032?

No fix has been published for CVE-2012-4032 yet. Limit exposure of the affected software until one is available.

## Is CVE-2012-4032 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4032 exists.

Public exploit code:

- WebsitePanel - 'ReturnUrl' Open Redirection (exploitdb)
- WebsitePanel before v1.2.2.1 - Open Redirect (nuclei): http/cves/2012/CVE-2012-4032.yaml

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2012-4032 and fix it if it is affected.

What it is: CVE-2012-4032 is a medium-severity vulnerability in n/a, published on 17 Jul 2012. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2012-4032 exists.

Affected product: n/a. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2012-4032/ (Markdown: https://insights.sbomify.com/CVE-2012-4032/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2012-4032
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2012-4032
- OSV: https://osv.dev/vulnerability/CVE-2012-4032

---
From sbomify Insights: https://insights.sbomify.com/CVE-2012-4032/
Summaries are generated and may contain mistakes; the official description above is the record.