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

> Remote attackers can execute arbitrary PHP code via remote file inclusion in Groupit, requiring immediate patching.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** 16 Mar 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-7q9p-vv66-jq48

## What is CVE-2007-1472?

CVE-2007-1472 is a medium-severity code injection vulnerability in n/a, published on 16 Mar 2007. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Variable overwrite vulnerability in groupit/base/groupit.start.inc in Groupit 2.00b5 allows remote attackers to conduct remote file inclusion attacks and execute arbitrary PHP code via arguments that are written to $_GLOBALS, as demonstrated using a URL in the c_basepath parameter to (1) content.php, (2) userprofile.php, (3) password.php, (4) dispatch.php, and (5) deliver.php in html/, and possibly (6) load.inc.php and related files.

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

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

It affects 1 product.


Products: T-Systems Solutions for Research Gmbh Groupit.

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

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

## Is CVE-2007-1472 being exploited?

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

Public exploit code:

- Groupit 2.00b5 - 'c_basepath' Remote File Inclusion (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2007-1472 is a medium-severity code injection vulnerability in n/a, published on 16 Mar 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-2007-1472 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-1472/ (Markdown: https://insights.sbomify.com/CVE-2007-1472/index.md)
```

## Sources

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

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