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

> Remote attackers can execute arbitrary SQL commands in Telephone Directory 2008 if magic_quotes_gpc is disabled, allowing data access or modification.

- **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:** 12 Jun 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-4cqq-5g7w-w4rv

## What is CVE-2008-2678?

CVE-2008-2678 is a high-severity SQL injection vulnerability in n/a, published on 12 Jun 2008. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in Telephone Directory 2008, when magic_quotes_gpc is disabled, allow remote attackers to execute arbitrary SQL commands via the (1) code parameter in a confirm_data action to edit1.php and the (2) id parameter to view_more.php.

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

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

It affects 1 product.


Products: Telephone Telephone Directory 2008.

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

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

## Is CVE-2008-2678 being exploited?

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

Public exploit code:

- Telephone Directory 2008 - SQL Injection / Cross-Site Scripting (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-2677](https://insights.sbomify.com/CVE-2008-2677/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

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

## Sources

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

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