CVE-2006-4433 json
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 handle…
published 20y ago modified 4mo ago also EUVD-2006-4421
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 1.8%
- EPSS 1.8% chance of exploitation in 30 days, percentile 79%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- hardened-php.net/advisory_052006.128.html advisory
- secunia.com/advisories/21573 advisory
Is CVE-2006-4433 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerExploit prediction
1.83% chance of exploitation in the next 30 days, higher than 79% of all scored CVEs (FIRST EPSS, 2026-11-14).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 7.5 | AV:N/AC:L/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
hardened-php.net
/advisory_052006.128.html
patch, vendor-advisory
-
secunia.com
/advisories/21573
third-party-advisory, patch, vendor-advisory
-
osvdb.org
/28233
vdb-entry
-
securityfocus.com
/archive/1/444263/100/0/threaded
mailing-list
-
securityreason.com
/securityalert/1466
third-party-advisory
-
osvdb.org
/28273
vdb-entry
-
vupen.com
/english/advisories/2006/3388
vdb-entry
Sources
- CVE List CVE-2006-4433
- NVD CVE-2006-4433
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.