# CVE-2008-7269: Open redirect in n/a

> Attackers can redirect users to malicious sites via the logout parameter, facilitating phishing attacks against SiteEngine users.

- **Severity:** Medium 5.8 (`AV:N/AC:M/Au:N/C:N/I:P/A:P`)
- **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:** 1 Dec 2010
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9vrp-p632-632f

## What is CVE-2008-7269?

CVE-2008-7269 is a medium-severity vulnerability in n/a, published on 1 Dec 2010. 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 api.php in SiteEngine 5.x allows user-assisted remote attackers to redirect users to arbitrary web sites and conduct phishing attacks via a URL in the forward parameter in a logout action.

Weakness: CWE-20 (Improper Input Validation)

## Which versions are affected by CVE-2008-7269?

It affects 1 product.


Products: Boka Siteengine.

## How do I fix CVE-2008-7269?

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

## Is CVE-2008-7269 being exploited?

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

Public exploit code:

- UC Gateway Investment SiteEngine 5.0 - 'api.php' Open Redirection (exploitdb)
- UC Gateway Investment SiteEngine v5.0 - Open Redirect (nuclei): http/cves/2008/CVE-2008-7269.yaml

## Other vulnerabilities in n/a

- [CVE-2008-7267](https://insights.sbomify.com/CVE-2008-7267/): SQL injection in n/a (high 7.5)
- [CVE-2010-4357](https://insights.sbomify.com/CVE-2010-4357/): SQL injection in n/a (high 7.5)
- [CVE-2008-7268](https://insights.sbomify.com/CVE-2008-7268/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-7269 and fix it if it is affected.

What it is: CVE-2008-7269 is a medium-severity vulnerability in n/a, published on 1 Dec 2010. 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-2008-7269 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-2008-7269/ (Markdown: https://insights.sbomify.com/CVE-2008-7269/index.md)
```

## Sources

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

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