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

> Remote attackers can execute arbitrary code in TotalCalendar via a URL in the inc_dir parameter, 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:** 24 Feb 2007
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-3f7x-25p9-vp9m

## What is CVE-2006-7055?

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

### Official description

PHP remote file inclusion vulnerability in index.php in TotalCalendar 2.30 and earlier allows remote attackers to execute arbitrary code via a URL in the inc_dir parameter, a different vector than CVE-2006-1922.

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

It affects 1 product.


Products: Sweetphp Totalcalendar.

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

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

## Is CVE-2006-7055 being exploited?

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

Public exploit code:

- TotalCalendar 2.30 - 'inc' Remote File Inclusion (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2007-3515](https://insights.sbomify.com/CVE-2007-3515/): SQL injection in n/a (critical 10.0)
- [CVE-2009-4973](https://insights.sbomify.com/CVE-2009-4973/): SQL injection in n/a (high 7.5)
- [CVE-2009-4974](https://insights.sbomify.com/CVE-2009-4974/): Path traversal in n/a (high 7.5)
- [CVE-2009-4928](https://insights.sbomify.com/CVE-2009-4928/): Code injection in n/a (high 7.5)
- [CVE-2009-1406](https://insights.sbomify.com/CVE-2009-1406/): Path traversal in n/a (medium 6.8)

## Fix prompt for AI coding agents

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

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

## Sources

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

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