# CVE-2007-6652: Code injection in n/a

> Remote attackers with admin privileges can execute arbitrary code via static code injection in XCMS due to improper redirect handling.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 4 Jan 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-cf9h-mc58-gqvq

## What is CVE-2007-6652?

CVE-2007-6652 is a high-severity code injection vulnerability in n/a, published on 4 Jan 2008. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

cpie.php in XCMS 1.83 and earlier sends a redirect to the web browser but does not exit, which allows remote attackers to conduct direct static code injection attacks and execute arbitrary code via the testo_0 parameter in a cpie admin action to index.php, which writes to dati/generali/footer.dtb (aka the XCMS footer).

Weakness: CWE-94 (Improper Control of Generation of Code)

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

It affects 1 product.


Products: Xcms Xcms.

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

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

## Is CVE-2007-6652 being exploited?

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

Public exploit code:

- XCMS 1.83 - Remote Command Execution (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-6604](https://insights.sbomify.com/CVE-2007-6604/): Path traversal in n/a (medium 5.0)
- [CVE-2007-5060](https://insights.sbomify.com/CVE-2007-5060/): Cross-site request forgery in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-6652 is a high-severity code injection vulnerability in n/a, published on 4 Jan 2008. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2007-6652 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-6652/ (Markdown: https://insights.sbomify.com/CVE-2007-6652/index.md)
```

## Sources

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

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