# CVE-2005-4009: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via vulnerable parameters in PHP Lite Calendar Express, potentially accessing or modifying database content.

- **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:** 5 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-hc75-g4hp-4wp6

## What is CVE-2005-4009?

CVE-2005-4009 is a high-severity SQL injection vulnerability in n/a, published on 5 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in PHP Lite Calendar Express 2.2 and earlier allow remote attackers to execute arbitrary SQL commands via the (1) cid and (2) catid parameters to (a) day.php, (b) week.php, (c) month.php, and (d) year.php.

## Which versions are affected by CVE-2005-4009?

It affects 1 product.


Products: Php Lite Calendar Express.

## How do I fix CVE-2005-4009?

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

## Is CVE-2005-4009 being exploited?

There is no known exploitation of CVE-2005-4009 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2007-3627](https://insights.sbomify.com/CVE-2007-3627/): SQL injection in n/a (high 7.5)
- [CVE-2006-2973](https://insights.sbomify.com/CVE-2006-2973/): SQL injection in n/a (high 7.5)
- [CVE-2006-1401](https://insights.sbomify.com/CVE-2006-1401/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-4009 and fix it if it is affected.

What it is: CVE-2005-4009 is a high-severity SQL injection vulnerability in n/a, published on 5 Dec 2005. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2005-4009 in the wild and no public exploit code.

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-2005-4009/ (Markdown: https://insights.sbomify.com/CVE-2005-4009/index.md)
```

## Sources

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

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