# CVE-2008-6104: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the eventid parameter in the admin interface of A4Desk PHP Event Calendar.

- **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:** 10 Feb 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-9p67-ppmf-hcm8

## What is CVE-2008-6104?

CVE-2008-6104 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2009. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

SQL injection vulnerability in A4Desk PHP Event Calendar allows remote attackers to execute arbitrary SQL commands via the eventid parameter to admin/index.php.

Weakness: CWE-89 (Improper Neutralization of Special Elements used in an SQL Command)

## Which versions are affected by CVE-2008-6104?

It affects 1 product.


Products: A4desk A4desk Flash Event Calendar.

## How do I fix CVE-2008-6104?

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

## Is CVE-2008-6104 being exploited?

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

Public exploit code:

- A4Desk Event Calendar - 'eventid' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-6103](https://insights.sbomify.com/CVE-2008-6103/): Code injection in n/a (medium 6.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2008-6104 and fix it if it is affected.

What it is: CVE-2008-6104 is a high-severity SQL injection vulnerability in n/a, published on 10 Feb 2009. 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-2008-6104 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-2008-6104/ (Markdown: https://insights.sbomify.com/CVE-2008-6104/index.md)
```

## Sources

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

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