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

> Remote attackers can inject arbitrary web script or HTML via the search query parameter in Esselbach Storyteller CMS.

- **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 needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 21 Dec 2005
- **Updated:** 7 Aug 2024
- **Also known as:** GHSA-xjq6-gc34-j23x

## What is CVE-2005-4433?

CVE-2005-4433 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official description

Cross-site scripting (XSS) vulnerability in search.php in Esselbach Storyteller CMS 1.8 allows remote attackers to inject arbitrary web script or HTML via the query parameter, which is used by the Search field.

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

It affects 1 product.


Products: Esselbach Internet Solutions Esselbach Storyteller Cms.

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

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

## Is CVE-2005-4433 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2005-4433 is a medium-severity cross-site scripting vulnerability in n/a, published on 21 Dec 2005. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: There is no known exploitation of CVE-2005-4433 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-4433/ (Markdown: https://insights.sbomify.com/CVE-2005-4433/index.md)
```

## Sources

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

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