# CVE-2000-0554: Information disclosure in n/a

> Remote attackers can obtain the real path of the Ceilidh directory via a hidden form field, exposing internal file system structure.

- **Severity:** Medium 5.0 (`AV:N/AC:L/Au:N/C:P/I:N/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:** 12 Jul 2000
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-8wr3-5grg-gmwh

## What is CVE-2000-0554?

CVE-2000-0554 is a medium-severity vulnerability in n/a, published on 12 Jul 2000. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Ceilidh allows remote attackers to obtain the real path of the Ceilidh directory via the translated_path hidden form field.

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

It affects 1 product.


Products: Lilikoi Ceilidh.

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

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

## Is CVE-2000-0554 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2000-0555](https://insights.sbomify.com/CVE-2000-0555/): Denial of service in n/a (medium 5.0)
- [CVE-2003-1531](https://insights.sbomify.com/CVE-2003-1531/): Cross-site scripting in n/a (medium 4.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2000-0554 is a medium-severity vulnerability in n/a, published on 12 Jul 2000. 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-2000-0554 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-2000-0554/ (Markdown: https://insights.sbomify.com/CVE-2000-0554/index.md)
```

## Sources

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

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