# CVE-2003-0025: SQL injection in n/a

> Remote attackers can exploit SQL injection in IMP webmail to access unauthorized database data and potentially escalate privileges.

- **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:** Yes
- **Published:** 15 Jan 2003
- **Updated:** 8 Aug 2024
- **Also known as:** DSA-229, GHSA-gxcm-7q4w-hgwc

## What is CVE-2003-0025?

CVE-2003-0025 is a high-severity SQL injection vulnerability in n/a, published on 15 Jan 2003. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in IMP 2.2.8 and earlier allow remote attackers to perform unauthorized database activities and possibly gain privileges via certain database functions such as check_prefs() in db.pgsql, as demonstrated using mailbox.php3.

## Which versions are affected by CVE-2003-0025?

It affects 1 product.


Products: Horde Imp.

## How do I fix CVE-2003-0025?

Upgrade to a fixed version.

## Is CVE-2003-0025 being exploited?

There is no known exploitation of CVE-2003-0025 in the wild and no public exploit code.

## Other vulnerabilities in n/a

- [CVE-2001-1257](https://insights.sbomify.com/CVE-2001-1257/): Cross-site scripting in n/a (high 7.5)
- [CVE-2004-0584](https://insights.sbomify.com/CVE-2004-0584/): Cross-site scripting in n/a (medium 6.8)
- [CVE-2002-2024](https://insights.sbomify.com/CVE-2002-2024/): Information disclosure in n/a (medium 5.3)
- [CVE-2010-0463](https://insights.sbomify.com/CVE-2010-0463/): Information disclosure in n/a (medium 5.0)
- [CVE-2000-0911](https://insights.sbomify.com/CVE-2000-0911/): Path traversal in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2003-0025 and fix it if it is affected.

What it is: CVE-2003-0025 is a high-severity SQL injection vulnerability in n/a, published on 15 Jan 2003. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0025 in the wild and no public exploit code.

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-2003-0025/ (Markdown: https://insights.sbomify.com/CVE-2003-0025/index.md)
```

## Sources

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

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