# CVE-2002-1410: Missing authorization in n/a

> Remote attackers can delete guestbook entries or reconfigure settings by accessing admin scripts without authentication.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 18 Mar 2003
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-wv5m-r3h8-56gx

## What is CVE-2002-1410?

CVE-2002-1410 is a high-severity missing authorization vulnerability in n/a, published on 18 Mar 2003. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Easy Guestbook CGI programs do not authenticate the administrator, which allows remote attackers to (1) delete entries via direct access of admin.cgi, or (2) reconfigure Guestbook via direct access of config.cgi.

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

It affects 2 products.


Products: Ben Chivers Ben Chivers Guestbook, Easy Scripts Archive Easy Guestbook.

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

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

## Is CVE-2002-1410 being exploited?

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

Public exploit code:

- Ben Chivers Easy Guestbook 1.0 - Administrative Access (exploitdb)

## Fix prompt for AI coding agents

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

What it is: CVE-2002-1410 is a high-severity missing authorization vulnerability in n/a, published on 18 Mar 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-2002-1410 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-2002-1410/ (Markdown: https://insights.sbomify.com/CVE-2002-1410/index.md)
```

## Sources

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

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