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

> Remote attackers can execute arbitrary scripts and perform privileged actions via dialog.php in CONTENTCustomizer, potentially leading to code execution.

- **Severity:** Medium 6.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/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:** 5 Nov 2007
- **Updated:** 3 Apr 2025
- **Also known as:** GHSA-fr7x-vvg8-f78x

## What is CVE-2007-5817?

CVE-2007-5817 is a medium-severity cross-site scripting vulnerability in n/a, published on 5 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

dialog.php in CONTENTCustomizer 3.1mp and earlier allows remote attackers to perform certain privileged actions via a (1) del, (2) delbackup, (3) res, or (4) ren action.  NOTE: this issue can be leveraged to conduct cross-site scripting (XSS) and possibly other attacks.

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

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

It affects 1 product.


Products: Contentcustomizer Contentcustomizer.

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

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

## Is CVE-2007-5817 being exploited?

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

Public exploit code:

- CONTENTCustomizer 3.1 - 'Dialog.php' Unauthorized Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-5816](https://insights.sbomify.com/CVE-2007-5816/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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