# CVE-2003-0304: Missing authorization in n/a

> Remote attackers can create administrator accounts by directly accessing the installation script, leading to full system compromise.

- **Severity:** Critical 10.0 (`AV:N/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 17 May 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-6cr3-qfqf-fc8q

## What is CVE-2003-0304?

CVE-2003-0304 is a critical missing authorization vulnerability in n/a, published on 17 May 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

one||zero (aka One or Zero) Helpdesk 1.4 rc4 allows remote attackers to create administrator accounts by directly calling the install.php Helpdesk Installation script.

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

It affects 1 product.


Products: Oneorzero Oneorzero Helpdesk.

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

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

## Is CVE-2003-0304 being exploited?

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

Public exploit code:

- OneOrZero Helpdesk 1.4 - 'install.php' Administrative Access (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2006-5474](https://insights.sbomify.com/CVE-2006-5474/): Weak cryptography in n/a (high 7.5)
- [CVE-2009-0886](https://insights.sbomify.com/CVE-2009-0886/): Path traversal in n/a (medium 5.0)
- [CVE-2003-0303](https://insights.sbomify.com/CVE-2003-0303/): SQL injection in n/a (medium 5.0)
- [CVE-2007-5727](https://insights.sbomify.com/CVE-2007-5727/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2003-0304 is a critical missing authorization vulnerability in n/a, published on 17 May 2003. 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-2003-0304 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-2003-0304/ (Markdown: https://insights.sbomify.com/CVE-2003-0304/index.md)
```

## Sources

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

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