# CVE-2004-0595: Cross-site scripting in n/a

> Attackers can bypass strip_tags filtering using null characters to inject malicious scripts, enabling cross-site scripting attacks against web applications.

- **Severity:** Medium 6.8 (`AV:N/AC:M/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:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 16 Jul 2004
- **Updated:** 8 Aug 2024
- **Also known as:** GHSA-h8wj-59vf-r37g

## What is CVE-2004-0595?

CVE-2004-0595 is a medium-severity cross-site scripting vulnerability in Php Php, published on 16 Jul 2004. 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

The strip_tags function in PHP 4.x up to 4.3.7, and 5.x up to 5.0.0RC3, does not filter null (\0) characters within tag names when restricting input to allowed tags, which allows dangerous tags to be processed by web browsers such as Internet Explorer and Safari, which ignore null characters and facilitate the exploitation of cross-site scripting (XSS) vulnerabilities.

## Which versions are affected by CVE-2004-0595?

It affects 8 products.


Products: Avaya Converged Communications Server, Avaya Integrated Management, Avaya S8300, Avaya S8500, Avaya S8700, Php Php, Redhat Fedora Core, Trustix Secure Linux.

## How do I fix CVE-2004-0595?

Upgrade to a fixed version.

## Is CVE-2004-0595 being exploited?

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

Public exploit code:

- PHP 4.x/5.0 - 'Strip_Tags()' Function Bypass (exploitdb)

## Other vulnerabilities in Php Php

- [CVE-2004-0495](https://insights.sbomify.com/CVE-2004-0495/): Privilege escalation in n/a (high 7.2)
- [CVE-2004-1235](https://insights.sbomify.com/CVE-2004-1235/): Race condition in n/a (medium 6.2)
- [CVE-2004-0594](https://insights.sbomify.com/CVE-2004-0594/): Race condition in n/a (medium 5.1)
- [CVE-2005-0003](https://insights.sbomify.com/CVE-2005-0003/): Memory corruption in n/a (low 2.1)
- [CVE-2004-0554](https://insights.sbomify.com/CVE-2004-0554/): Denial of service in n/a (low 2.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2004-0595 and fix it if it is affected.

What it is: CVE-2004-0595 is a medium-severity cross-site scripting vulnerability in Php Php, published on 16 Jul 2004. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2004-0595 exists.

Affected product: Php Php. 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-2004-0595/ (Markdown: https://insights.sbomify.com/CVE-2004-0595/index.md)
```

## Sources

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

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