CVE-2004-0595

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • No confirmed exploitation signals yet
CISA-KEV: Not listedEPSS: 45%CVSS: —Exploit: NoneExposed: 0

A fix is available — apply it.

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.

CVSS v3
—
EG Score
0.0(none)
EPSS
98.6%
KEV
Not listed

Published

July 27, 2004

Last Modified

June 16, 2026

References (36)

Patch Availability(4)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatpatch2005-11-02redhat
redhatpatch2004-07-23redhat
redhatphp-0:4.3.2-11.1.ent2004-07-19redhat
redhatpatch2004-07-19redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(4)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 3× in last 7d / 19× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-13 06:07 UTCEPSS rescore
  2. 2026-07-11 08:22 UTCEPSS rescore
  3. 2026-07-11 08:22 UTCEPSS rescore
  4. 2026-07-02 14:00 UTCEPSS rescore
  5. 2026-06-29 14:02 UTCEPSS rescore
  6. 2026-06-29 14:02 UTCEPSS rescore
  7. 2026-06-28 04:52 UTCEPSS rescore
  8. 2026-06-23 21:29 UTCEPSS rescore
  9. 2026-06-22 14:22 UTCEPSS rescore
  10. 2026-06-21 01:56 UTCEPSS rescore
  11. 2026-06-18 17:49 UTCEPSS rescore
  12. 2026-06-18 17:49 UTCEPSS rescore
  13. 2026-06-17 17:49 UTCEPSS rescore
  14. 2026-06-17 17:49 UTCEPSS rescore
  15. 2026-06-16 17:49 UTCEPSS rescore
  16. 2026-06-16 17:49 UTCEPSS rescore
  17. 2026-06-15 17:43 UTCEPSS rescore
  18. 2026-06-14 23:13 UTCEPSS rescore
  19. 2026-06-14 23:13 UTCEPSS rescore
  20. 2026-06-13 22:56 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-11 13:55 UTCEPSS rescore
  23. 2026-06-10 22:13 UTCEPSS rescore
  24. 2026-06-10 13:17 UTCEPSS rescore
  25. 2026-06-08 14:13 UTCEPSS rescore
Show 26 more
  1. 2026-06-06 13:44 UTCEPSS rescore
  2. 2026-06-06 13:44 UTCEPSS rescore
  3. 2026-06-06 13:44 UTCEPSS rescore
  4. 2026-06-05 22:43 UTCEPSS rescore
  5. 2026-06-05 22:43 UTCEPSS rescore
  6. 2026-06-04 13:09 UTCEPSS rescore
  7. 2026-06-02 20:10 UTCEPSS rescore
  8. 2026-05-31 22:28 UTCEPSS rescore
  9. 2026-05-31 16:11 UTCEG score recompute
  10. 2026-05-31 16:11 UTCVendor advisory
  11. 2026-05-31 16:11 UTCGHSA enrichment
  12. 2026-05-31 00:13 UTCEPSS rescore
  13. 2026-05-31 00:13 UTCEPSS rescore
  14. 2026-05-29 13:40 UTCEPSS rescore
  15. 2026-05-29 13:40 UTCEPSS rescore
  16. 2026-05-28 13:42 UTCEPSS rescore
  17. 2026-05-28 13:42 UTCEPSS rescore
  18. 2026-05-28 13:42 UTCEPSS rescore
  19. 2026-05-27 13:37 UTCEPSS rescore
  20. 2026-05-26 07:16 UTCEPSS rescore
  21. 2026-05-26 07:16 UTCEPSS rescore
  22. 2026-05-22 21:15 UTCEPSS rescore
  23. 2026-05-20 11:20 UTCEPSS rescore
  24. 2026-05-20 11:20 UTCEPSS rescore
  25. 2026-05-18 21:29 UTCEPSS rescore
  26. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-24280✓ verified
    First seen Jul 14, 2004

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

    Open source ↗

Frequently asked(4)

What is CVE-2004-0595?
CVE-2004-0595 is a none vulnerability published on July 27, 2004. 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…
When was CVE-2004-0595 disclosed?
CVE-2004-0595 was first published in the National Vulnerability Database on July 27, 2004, with the most recent update on June 16, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2004-0595 actively exploited?
CVE-2004-0595 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.6% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2004-0595?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2004-0595, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2004-0595

Explore →

Is Your Infrastructure Affected by CVE-2004-0595?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs