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

> Remote attackers can execute arbitrary SQL commands to create accounts and read, modify, or delete backend database data in Layton HelpBox.

- **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:** 21 Nov 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-cqf6-wpgm-m6gf

## What is CVE-2004-2551?

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

### Official description

Multiple SQL injection vulnerabilities in Layton HelpBox 3.0.1 allow remote attackers to execute arbitrary SQL commands via (1) the sys_comment_id parameter in editcommentenduser.asp, (2) the sys_suspend_id parameter in editsuspensionuser.asp, (3) the table parameter in export_data.asp, (4) the sys_analgroup parameter in manageanalgrouppreference.asp, (5) the sys_asset_id parameter in quickinfoassetrequests.asp, (6) the sys_eusername parameter in quickinfoenduserrequests.asp, and the sys_request_id parameter in (7) requestauditlog.asp, (8) requestcommentsenduser.asp, (9) selectrequestapplytemplate.asp, and (10) selectrequestlink.asp, resulting in an ability to create a new HelpBox user account and read, modify, or delete data from the backend database.

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

It affects 1 product.


Products: Layton Technology Helpbox.

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

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

## Is CVE-2004-2551 being exploited?

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

Public exploit code:

- Layton Technology HelpBox 3.0.1 - Multiple SQL Injections (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2012-4971](https://insights.sbomify.com/CVE-2012-4971/): SQL injection in n/a (high 7.5)
- [CVE-2007-5401](https://insights.sbomify.com/CVE-2007-5401/): File upload in n/a (medium 6.5)
- [CVE-2007-5402](https://insights.sbomify.com/CVE-2007-5402/): SQL injection in n/a (medium 6.5)
- [CVE-2012-4976](https://insights.sbomify.com/CVE-2012-4976/): Information disclosure in n/a (medium 5.0)
- [CVE-2012-4977](https://insights.sbomify.com/CVE-2012-4977/): Information disclosure in n/a (medium 5.0)

## Fix prompt for AI coding agents

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

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

## Sources

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

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