# CVE-2002-0096: Privilege escalation in n/a

> A flaw in Geeklog installation leaves a stale database record, granting the first new user unintended administrative privileges.

- **Severity:** High 7.2 (`AV:L/AC:L/Au:N/C:C/I:C/A:C`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 25 Jun 2002
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-j9f3-2w77-j5qj

## What is CVE-2002-0096?

CVE-2002-0096 is a high-severity vulnerability in n/a, published on 25 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

The installation of Geeklog 1.3 creates an extra group_assignments record which is not properly deleted, which causes the first newly created user to be added to the GroupAdmin and UserAdmin groups, which could provide that user with administrative privileges that were not intended.

## Which versions are affected by CVE-2002-0096?

It affects 1 product.


Products: Geeklog Geeklog.

## How do I fix CVE-2002-0096?

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

## Is CVE-2002-0096 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2006-1069](https://insights.sbomify.com/CVE-2006-1069/): Privilege escalation in n/a (critical 10.0)
- [CVE-2006-2698](https://insights.sbomify.com/CVE-2006-2698/): Information disclosure in n/a (high 7.8)
- [CVE-2010-4933](https://insights.sbomify.com/CVE-2010-4933/): SQL injection in n/a (high 7.5)
- [CVE-2007-2793](https://insights.sbomify.com/CVE-2007-2793/): Code injection in n/a (high 7.5)
- [CVE-2007-0810](https://insights.sbomify.com/CVE-2007-0810/): Code injection in n/a (high 7.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2002-0096 and fix it if it is affected.

What it is: CVE-2002-0096 is a high-severity vulnerability in n/a, published on 25 Jun 2002. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2002-0096 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-2002-0096/ (Markdown: https://insights.sbomify.com/CVE-2002-0096/index.md)
```

## Sources

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

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