# CVE-2006-7024: Code injection in n/a

> Remote attackers can execute arbitrary PHP code in Harpia CMS via remote file inclusion in multiple parameters.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 15 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-c4hp-rx37-pcpf

## What is CVE-2006-7024?

CVE-2006-7024 is a high-severity code injection vulnerability in n/a, published on 15 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple PHP remote file inclusion vulnerabilities in Harpia CMS 1.0.5 and earlier allow remote attackers to execute arbitrary PHP code via a URL in the (1) func_prog parameter to (a) preload.php and (b) index.php; (2) header_prog parameter to (c) missing.php and (d) email.php, (e) files.php, (f) headlines.php, (g) search.php, (h) topics.php, and (i) users.php in _mods/; (3) theme_root parameter to (j) footer.php, (k) header.php, (l) pfooter.php, and (m) pheader.php in _inc; (4) mod_root parameter to _inc/header.php; and the (5) mod_dir and (6) php_ext parameters to (n) _inc/web_statsConfig.php.

## Which versions are affected by CVE-2006-7024?

It affects 1 product.


Products: Harpia Harpia Cms.

## How do I fix CVE-2006-7024?

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

## Is CVE-2006-7024 being exploited?

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

Public exploit code:

- Harpia CMS 1.0.5 - Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2006-7024 and fix it if it is affected.

What it is: CVE-2006-7024 is a high-severity code injection vulnerability in n/a, published on 15 Feb 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2006-7024 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-2006-7024/ (Markdown: https://insights.sbomify.com/CVE-2006-7024/index.md)
```

## Sources

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

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