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

> Authenticated users with specific permissions can execute arbitrary SQL commands via the Ajax Checklist module save function.

- **Severity:** Medium 6.0 (`AV:N/AC:M/Au:S/C:P/I:P/A:P`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 28 Jan 2009
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-6f6h-rwhv-q9gg

## What is CVE-2008-5998?

CVE-2008-5998 is a medium-severity SQL injection vulnerability in n/a, published on 28 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in the ajax_checklist_save function in the Ajax Checklist module 5.x before 5.x-1.1 for Drupal allow remote authenticated users, with "update ajax checklists" permissions, to execute arbitrary SQL commands via a save operation, related to the (1) nid, (2) qid, and (3) state parameters.

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

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

It affects 1 product.


Products: Drupal Ajax Checklist.

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

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

## Is CVE-2008-5998 being exploited?

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

Public exploit code:

- Drupal Module Ajax Checklist 5.x-1.0 - Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2008-5999](https://insights.sbomify.com/CVE-2008-5999/): Cross-site scripting in n/a (low 3.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2008-5998 is a medium-severity SQL injection vulnerability in n/a, published on 28 Jan 2009. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2008-5998 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-5998/ (Markdown: https://insights.sbomify.com/CVE-2008-5998/index.md)
```

## Sources

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

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