CVE-2006-4433: n/a vulnerability

CVE-2006-4433: PHP before 4.4.3 and 5.x before 5.1.4 does not limit the character set of the session identifier (PHPSESSID...

PHP before 4.4.3 and 5.x before 5.1.4 does not limit the character set of the session identifier (PHPSESSID) for third party session handlers, which might make it easier for remote attackers to exploit other vulnerabilities by inserting PHP code into the PHPSESSID, which is stored in the session file. NOTE: it could be argued that this not a vulnerability in PHP itself, rather a design limitation that enables certain attacks against session handlers that do not account for this limitation.

UnknownCVSS not scoredNot KEV-listedUpdatedAug 7, 2024, 19:06 UTC (UTC+00:00)

Security readout for executives and security teams

This is a legacy PHP session-handling weakness. Older PHP versions allowed unsafe characters in PHPSESSID values for third-party session handlers. In some deployments, that could help an attacker turn a session file into a vehicle for another vulnerability. Business urgency is mainly for very old PHP systems or custom session storage. Exposure is most likely in legacy PHP 4.x or early PHP 5.x applications using third-party or custom session handlers. Systems on supported PHP versions are unlikely to be exposed to this specific issue. The source bundle does not identify affected third-party handlers or products. Treat this as a legacy-system hygiene issue unless affected PHP versions are still present. The priority is finding and retiring unsupported PHP deployments, especially internet-facing applications with custom session handling. No source provided evidence of active exploitation. Mitigation focus: Upgrade any affected PHP runtime beyond 4.4.3 or 5.1.4, preferably to a supported release.; Review custom or third-party session handlers for strict PHPSESSID validation.; Reject session identifiers containing characters outside the expected safe session ID set..

Prepared: Jun 29, 2026, 10:45 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-2006-4433 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: Aug 29, 2006, 00: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

1Source 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

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.