# CVE-2007-5695: Open redirect in n/a

> Remote attackers can redirect users to arbitrary websites via the forward parameter in the login action, requiring user interaction to click a crafted link.

- **Severity:** Medium 6.4 (`AV:N/AC:L/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:** Yes
- **Published:** 29 Oct 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-j7r5-h76v-5p9v

## What is CVE-2007-5695?

CVE-2007-5695 is a medium-severity vulnerability in n/a, published on 29 Oct 2007. 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 command.php in SiteBar 3.3.8 allows remote attackers to redirect users to arbitrary web sites via a URL in the forward parameter in a Log In action.

Weakness: CWE-59 (Improper Link Resolution Before File Access)

## Which versions are affected by CVE-2007-5695?

It affects 1 product.


Products: Sitebar Sitebar.

## How do I fix CVE-2007-5695?

Upgrade to a fixed version.

## Is CVE-2007-5695 being exploited?

There is no known exploitation of CVE-2007-5695 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-5491](https://insights.sbomify.com/CVE-2007-5491/): Path traversal in n/a (critical 9.0)
- [CVE-2007-2088](https://insights.sbomify.com/CVE-2007-2088/): Code injection in n/a (high 7.5)
- [CVE-2007-5694](https://insights.sbomify.com/CVE-2007-5694/): Path traversal in n/a (medium 6.8)
- [CVE-2007-5693](https://insights.sbomify.com/CVE-2007-5693/): Code injection in n/a (medium 6.0)
- [CVE-2007-5492](https://insights.sbomify.com/CVE-2007-5492/): Code injection in n/a (medium 4.6)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2007-5695 and fix it if it is affected.

What it is: CVE-2007-5695 is a medium-severity vulnerability in n/a, published on 29 Oct 2007. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-5695 in the wild and no public exploit code.

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-2007-5695/ (Markdown: https://insights.sbomify.com/CVE-2007-5695/index.md)
```

## Sources

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

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