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

> Remote attackers can execute arbitrary SQL statements via vulnerable parameters in phpGroupWare, 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 stated
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 6 Feb 2005
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-9jjp-m5p6-8984

## What is CVE-2004-1383?

CVE-2004-1383 is a high-severity SQL injection vulnerability in n/a, published on 6 Feb 2005. It can be exploited over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in phpGroupWare 0.9.16.003 and earlier allow remote attackers to execute arbitrary SQL statements via the (1) order, (2) project_id, (3) pro_main, or (4) hours_id parameters to index.php or (5) ticket_id to viewticket_details.php.

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

It affects 1 product.


Products: Phpgroupware Phpgroupware.

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

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

## Is CVE-2004-1383 being exploited?

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

Public exploit code:

- phpGroupWare 0.9.x - 'viewticket_details.php?ticket_id' SQL Injection (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2004-2406](https://insights.sbomify.com/CVE-2004-2406/): Other in n/a (critical 10.0)
- [CVE-2004-2407](https://insights.sbomify.com/CVE-2004-2407/): Unknown vulnerability in phpGroupWare before 0.9.14.002 has unknown attack vectors and impact, related to a "security hole" in the Setup/Config functionality. (critical 10.0)
- [CVE-2003-0599](https://insights.sbomify.com/CVE-2003-0599/): Path traversal in n/a (critical 10.0)
- [CVE-2001-0043](https://insights.sbomify.com/CVE-2001-0043/): Code injection in n/a (critical 10.0)
- [CVE-2010-0404](https://insights.sbomify.com/CVE-2010-0404/): SQL injection in n/a (high 7.5)

## Fix prompt for AI coding agents

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

What it is: CVE-2004-1383 is a high-severity SQL injection vulnerability in n/a, published on 6 Feb 2005. It can be exploited 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-1383 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-1383/ (Markdown: https://insights.sbomify.com/CVE-2004-1383/index.md)
```

## Sources

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

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