# CVE-2005-0888: Cross-site scripting in n/a

> Remote attackers can inject arbitrary web script or HTML via class or method names in Double Choco Latte.

- **Severity:** Medium 4.3 (`AV:N/AC:M/Au:N/C:N/I:P/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not stated
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Mar 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-vc4f-x28m-p38x

## What is CVE-2005-0888?

CVE-2005-0888 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Mar 2005. It can be exploited over the network, and only if a user opens a file or follows a link.

### Official description

Multiple cross-site scripting (XSS) vulnerabilities in functions.inc.php for Double Choco Latte 0.9.4.3 allow remote attackers to inject arbitrary web script or HTML via the (1) class or (2) method name.

## Which versions are affected by CVE-2005-0888?

It affects 1 product.


Products: Michael Dean Double Choco Latte.

## How do I fix CVE-2005-0888?

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

## Is CVE-2005-0888 being exploited?

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

## Other vulnerabilities in n/a

- [CVE-2005-0887](https://insights.sbomify.com/CVE-2005-0887/): Code injection in n/a (high 7.5)
- [CVE-2002-1039](https://insights.sbomify.com/CVE-2002-1039/): Path traversal in n/a (medium 5.0)
- [CVE-2002-1037](https://insights.sbomify.com/CVE-2002-1037/): Cross-site scripting in n/a (medium 5.0)
- [CVE-2002-1038](https://insights.sbomify.com/CVE-2002-1038/): File upload in n/a (medium 5.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2005-0888 and fix it if it is affected.

What it is: CVE-2005-0888 is a medium-severity cross-site scripting vulnerability in n/a, published on 26 Mar 2005. It can be exploited over the network, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-0888 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-2005-0888/ (Markdown: https://insights.sbomify.com/CVE-2005-0888/index.md)
```

## Sources

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

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