# CVE-2007-0706: Cross-site scripting in n/a

> Remote attackers can bypass web content zone restrictions in Internet Explorer RSS bars via malicious scripts in RSS data, requiring user interaction.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/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:** 4 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-g99p-rf3w-gv75

## What is CVE-2007-0706?

CVE-2007-0706 is a high-severity cross-site scripting vulnerability in n/a, published on 4 Feb 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

Cross-zone scripting vulnerability in Darksky RSS bar for Internet Explorer before 1.29, RSS bar for Sleipnir before 1.29, and RSS bar for unDonut before 1.29 allows remote attackers to bypass Web content zone restrictions via certain script contained in RSS data.  NOTE: some of these details are obtained from third party information.

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

It affects 1 product.


Products: Fenrir Darksky Rss Bar.

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

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

## Is CVE-2007-0706 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0706 is a high-severity cross-site scripting vulnerability in n/a, published on 4 Feb 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-0706 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-0706/ (Markdown: https://insights.sbomify.com/CVE-2007-0706/index.md)
```

## Sources

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

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