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

> Remote attackers can inject arbitrary web script or HTML via the directory parameter in PHPSlideShow, potentially compromising user sessions.

- **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:** 27 Nov 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-5hw9-7c3p-xqf9

## What is CVE-2007-6135?

CVE-2007-6135 is a medium-severity cross-site scripting vulnerability in n/a, published on 27 Nov 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 phpslideshow.php in PHPSlideShow 0.9.9.2, and possibly earlier, allows remote attackers to inject arbitrary web script or HTML via the directory parameter. NOTE: this issue was originally reported for toonchapter8.php, but this is probably a site-specific name, since the PHPSlideShow distribution does not contain that file.

Weakness: CWE-79 (Improper Neutralization of Input During Web Page Generation)

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

It affects 1 product.


Products: Phpslideshow Phpslideshow.

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

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

## Is CVE-2007-6135 being exploited?

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

Public exploit code:

- PHPSlideShow 0.9.9 - 'Directory' Cross-Site Scripting (exploitdb)

## Fix prompt for AI coding agents

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

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

## Sources

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

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