# CVE-2000-0688: Auth bypass in n/a

> Remote attackers can bypass authentication to change the administrator password and gain Account Manager privileges in Subscribe Me LITE.

- **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:** 21 Sep 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-x7q8-c93w-mjgm

## What is CVE-2000-0688?

CVE-2000-0688 is a high-severity authentication bypass vulnerability in n/a, published on 21 Sep 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Subscribe Me LITE does not properly authenticate attempts to change the administrator password, which allows remote attackers to gain privileges for the Account Manager by directly calling the subscribe.pl script with the setpwd parameter.

## Which versions are affected by CVE-2000-0688?

It affects 1 product.


Products: Cgi Script Center Subscribe Me Lite.

## How do I fix CVE-2000-0688?

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

## Is CVE-2000-0688 being exploited?

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

Public exploit code:

- CGI Script Center Subscribe Me Lite 2.0 - Administrative Password Alteration (1) (exploitdb)
- CGI Script Center Subscribe Me Lite 2.0 - Administrative Password Alteration (2) (exploitdb)

## Other vulnerabilities in n/a

- [CVE-2001-0086](https://insights.sbomify.com/CVE-2001-0086/): Missing authorization in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2000-0688 and fix it if it is affected.

What it is: CVE-2000-0688 is a high-severity authentication bypass vulnerability in n/a, published on 21 Sep 2000. 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-2000-0688 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-2000-0688/ (Markdown: https://insights.sbomify.com/CVE-2000-0688/index.md)
```

## Sources

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

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