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

> Remote attackers can exploit SQL injection in the 4nalbum plugin to gain privileges or modify database contents.

- **Severity:** High 7.5 (`AV:N/AC:L/Au:N/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:** 10 May 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-76hg-76m7-348w

## What is CVE-2004-1821?

CVE-2004-1821 is a high-severity SQL injection vulnerability in n/a, published on 10 May 2005. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

SQL injection vulnerability in 4nalbum 0.92 for PHP-Nuke 6.5 through 7.0 allows remote attackers to gain privileges or perform unauthorized database operations via the gid parameter.

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

It affects 1 product.


Products: Warpspeed 4nalbum Module.

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

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

## Is CVE-2004-1821 being exploited?

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

Public exploit code:

- WarpSpeed 4nAlbum Module 0.92 - 'modules.php?gid' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-1820](https://insights.sbomify.com/CVE-2004-1820/): Code injection in n/a (high 7.5)
- [CVE-2004-1819](https://insights.sbomify.com/CVE-2004-1819/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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