LiveActive security incident?Get immediate response
CVE Record

CVE-2004-0595: 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) character...

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.

UnknownCVSS not scoredNot KEV-listedUpdated
Glexia's TakeAutomated analysis

Security readout for executives and security teams

This is an old PHP input-filtering flaw. Some PHP versions could leave dangerous HTML tags intact when null characters were inserted, letting certain browsers treat the content as executable script. The business risk is mainly legacy web applications that still rely on vulnerable PHP filtering for user-supplied HTML. Exposure is most likely in legacy PHP applications using strip_tags to sanitize untrusted HTML while allowing some tags. Current, supported PHP deployments are less likely to be affected, but old embedded systems, abandoned sites, or vendor appliances should be checked. Prioritize this for legacy PHP estate review, not emergency response. No active exploitation is cited, but the flaw affects web-facing input handling and can support browser-based account compromise where old PHP remains deployed. Mitigation focus: Inventory PHP versions and identify PHP 4.x through 4.3.7 or PHP 5.x through 5.0.0RC3.; Apply the relevant vendor security updates for the operating system or PHP distribution.; Retire or isolate legacy PHP applications that cannot be updated promptly..

Prepared

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cve · low confidence lookup

CVE-2004-0595 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Unknown
CVSS
Not scored
Known Exploited
No
Published
Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

0CVSS vectors
0Timeline events
0ADP providers
3Source links

CVSS and timeline data

No CVSS vectors or timeline events were available in the normalized CVE source material.

Source materials

Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
n/an/an/aListed
Weakness

CWE details

No CWE listed

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.