# CVE-2004-2295: SQL injection in n/a

> Remote attackers can execute arbitrary SQL commands via the order parameter in the Reviews module, potentially compromising database integrity and confidentiality.

- **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:** 4 Aug 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-4m8x-fc8r-wmqm

## What is CVE-2004-2295?

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

### Official description

SQL injection vulnerability in the Reviews module in PHP-Nuke 6.0 to 7.3 allows remote attackers to execute arbitrary SQL commands via the order parameter.

## Which versions are affected by CVE-2004-2295?


## How do I fix CVE-2004-2295?

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

## Is CVE-2004-2295 being exploited?

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

Public exploit code:

- PHP-Nuke 6.x/7.x Reviews Module - 'order' SQL Injection (exploitdb)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-2295 and fix it if it is affected.

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

## Sources

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

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