# CVE-2007-0660: DotNetNuke Vulnerable to XSS in Pass-Through Values

> Remote attackers can inject arbitrary web script or HTML via the IFrame module, potentially leading to session hijacking or malicious actions.

- **Severity:** Medium 6.8 (`AV:N/AC:M/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 1 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xr96-7ccp-pg5c

## What is CVE-2007-0660?

CVE-2007-0660 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Feb 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in the IFrame module before 03.02.01 for DotNetNuke (DNN) allows remote attackers to inject arbitrary web script or HTML via unspecified vectors related to "Pass through values."

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

2 open source packages ship an affected version, including DotNetNuke.Core. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `DotNetNuke.Core` | NuGet | All versions | 03.02.01 |
| `DotNetNuke.Core` | NuGet | All versions | 03.02.01 |

Products: Dotnetnuke Dotnetnuke Iframe.

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

Upgrade DotNetNuke.Core to 03.02.01 or later.

## Is CVE-2007-0660 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2007-0660 is a medium-severity cross-site scripting vulnerability in n/a, published on 1 Feb 2007. Any signed-in user can exploit it over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2007-0660 in the wild and no public exploit code.

Affected packages and fixed versions:
- DotNetNuke.Core (NuGet): affected all versions; fixed in 03.02.01
- DotNetNuke.Core (NuGet): affected all versions; fixed in 03.02.01

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

## Sources

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

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