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

> Remote attackers can inject arbitrary SQL via multiple parameters in DeskPRO, enabling unauthorized data access and modification.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Oct 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-vc76-xf92-jm9m

## What is CVE-2003-0874?

CVE-2003-0874 is a medium-severity SQL injection vulnerability in n/a, published on 25 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Multiple SQL injection vulnerabilities in DeskPRO 1.1.0 and earlier allow remote attackers to insert arbitrary SQL and conduct unauthorized activities via (1) the cat parameter in faq.php, (2) the article parameter in faq.php, (3) the tickedid parameter in view.php, and (4) the Password entry on the logon screen.

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

It affects 1 product.


Products: Deskpro Deskpro.

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

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

## Is CVE-2003-0874 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2020-11467](https://insights.sbomify.com/CVE-2020-11467/): Deserialization in n/a (critical 9.1)
- [CVE-2020-11465](https://insights.sbomify.com/CVE-2020-11465/): Missing authorization in n/a (high 8.8)
- [CVE-2020-11466](https://insights.sbomify.com/CVE-2020-11466/): Missing authorization in n/a (high 7.6)
- [CVE-2020-11463](https://insights.sbomify.com/CVE-2020-11463/): Missing authorization in n/a (high 7.5)
- [CVE-2021-35391](https://insights.sbomify.com/CVE-2021-35391/): Server-side request forgery in n/a (high 7.2)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0874 is a medium-severity SQL injection vulnerability in n/a, published on 25 Oct 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2003-0874 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-0874/ (Markdown: https://insights.sbomify.com/CVE-2003-0874/index.md)
```

## Sources

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

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