CVE-2007-1522 json
Double free vulnerability in the session extension in PHP 5.2.0 and 5.2.1 allows context-dependent attackers to execute arbitrary code via…
published 19y ago modified 4mo ago also EUVD-2007-1516
- cvss
- 6.8
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 6.7%
- EPSS 6.7% chance of exploitation in 30 days, percentile 94%
- public exploits
- 1
- Exploit-DB
Summary
Double free vulnerability in the session extension in PHP 5.2.0 and 5.2.1 allows context-dependent attackers to execute arbitrary code via illegal characters in a session identifier, which is rejected by an internal session storage module, which calls the session identifier generator with an improper environment, leading to code execution when the generator is interrupted, as demonstrated by triggering a memory limit violation or certain PHP errors.
Is CVE-2007-1522 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 FencerTimeline
- First public exploit (EDB-3480)
- Published
Exploit prediction
6.71% chance of exploitation in the next 30 days, higher than 94% of all scored CVEs (FIRST EPSS, 2026-11-14).
Exploits and checks
- EDB-3480 PHP 5.2.0/5.2.1 - Rejected Session ID Double-Free local, 2007-03-14
- php-security.org http://www.php-security.org/MOPB/MOPB-23-2007.html referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| NVD | 2.0 | 6.8 | AV:N/AC:M/Au:N/C:P/I:P/A:P |
Classification
- Technology feeds
References
-
php-security.org
/MOPB/MOPB-23-2007.html
exploit, vendor-advisory
-
novell.com
/linux/security/advisories/2007_32_php.html
vendor-advisory
-
vupen.com
/english/advisories/2007/0960
vdb-entry
-
secunia.com
/advisories/25056
third-party-advisory
-
secunia.com
/advisories/24505
third-party-advisory
-
securityfocus.com
/bid/22971
vdb-entry
Sources
- CVE List CVE-2007-1522
- NVD CVE-2007-1522
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.