CVE-2015-4598: n/a vulnerability

CVE-2015-4598: PHP before 5.4.42, 5.5.x before 5.5.26, and 5.6.x before 5.6.10 does not ensure that pathnames lack %00 seq...

PHP before 5.4.42, 5.5.x before 5.5.26, and 5.6.x before 5.6.10 does not ensure that pathnames lack %00 sequences, which might allow remote attackers to read or write to arbitrary files via crafted input to an application that calls (1) a DOMDocument save method or (2) the GD imagepsloadfont function, as demonstrated by a filename\0.html attack that bypasses an intended configuration in which client users may write to only .html files.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 6, 2024, 06:18 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy PHP flaw where certain file-handling paths could mishandle encoded null-byte sequences. If an exposed application passed attacker-controlled filenames into affected DOMDocument or GD functions, file extension restrictions could be bypassed, potentially allowing unauthorized file reads or writes. Exposure is most likely in legacy PHP 5.x deployments below the fixed releases, especially applications accepting user-controlled file paths for DOMDocument save operations or GD font loading. Vendor-packaged PHP may include backported fixes, so package advisory status matters more than raw version strings alone. Treat this as high priority where legacy PHP applications remain internet-facing or process user-controlled filenames. For fully upgraded environments, urgency is lower but validation is still warranted because PHP 5.x is obsolete and may carry broader unsupported-risk exposure. Mitigation focus: Upgrade PHP to 5.4.42, 5.5.26, 5.6.10, or vendor-fixed packages.; Prioritize migration away from unsupported PHP 5.x branches.; Review vendor advisories from PHP, Debian, Red Hat, and Oracle for package-specific fixes..

Prepared: Jun 13, 2026, 14:22 UTC (UTC+00:00)

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-2015-4598 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: May 16, 2016, 10:00 UTC (UTC+00:00)

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

2Source links

CVSS and timeline data

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

Source materials

CVE List V5 sourceCVE List V5
https://bugs.php.net/bug.php?id=69719CVE reference · x_refsource_CONFIRM

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.