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

> Remote attackers can inject arbitrary web script or HTML via the pageid parameter in WebStudio, requiring user interaction to execute.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/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:** 6 Jun 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-948g-p2xw-85hh

## What is CVE-2007-3070?

CVE-2007-3070 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jun 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-site scripting (XSS) vulnerability in index.php in BDigital Web Solutions WebStudio allows remote attackers to inject arbitrary web script or HTML via the pageid parameter.

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

It affects 1 product.


Products: Bdigital Web Solutions Webstudio Cms.

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

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

## Is CVE-2007-3070 being exploited?

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

Public exploit code:

- WebStudio CMS - 'index.php' Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5336](https://insights.sbomify.com/CVE-2008-5336/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-3070 is a medium-severity cross-site scripting vulnerability in n/a, published on 6 Jun 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: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-3070 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-2007-3070/ (Markdown: https://insights.sbomify.com/CVE-2007-3070/index.md)
```

## Sources

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

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