# CVE-2008-3554: SQL injection vulnerability in index.php in Discuz!


- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Fix available:** No
- **Published:** 8 Aug 2008
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-8232-c5fm-5f68

## What is CVE-2008-3554?

CVE-2008-3554 is a high-severity vulnerability in n/a, published on 8 Aug 2008. 

### Official description

SQL injection vulnerability in index.php in Discuz! 6.0.1 allows remote attackers to execute arbitrary SQL commands via the searchid parameter in a search action.

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

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

It affects 1 product.


Products: Comsenz Discuz.

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

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

## Is CVE-2008-3554 being exploited?

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

Public exploit code:

- Discuz! 6.0.1 - 'searchid' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-3554 is a high-severity vulnerability in n/a, published on 8 Aug 2008. 
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-3554 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-3554/ (Markdown: https://insights.sbomify.com/CVE-2008-3554/index.md)
```

## Sources

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

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