CVE-2007-0905 json
PHP before 5.2.1 allows attackers to bypass safe_mode and open_basedir restrictions via unspecified vectors in the session extension.
published 2007-02-13 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-0899
- cvss
- 7.5
- version 2.0, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 2.5%
- EPSS 2.5% chance of exploitation in 30 days, percentile 85%
- public exploits
- 0
- none known
Summary
PHP before 5.2.1 allows attackers to bypass safe_mode and open_basedir restrictions via unspecified vectors in the session extension. NOTE: it is possible that this issue is a duplicate of CVE-2006-6383.
Patch / fix
Vendor advisories
What the vendors themselves say about their products: affected, fixed or not affected, and what to do.
red hat product security vex CVE-2007-0905 updated
php session extension safe_mode/open_basedir bypass
-
Red Hat All currently supported Red Hat productsnot affected: vulnerable code not present
Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf
Exploit prediction
2.55% chance of exploitation in the next 30 days, higher than 85% of all scored CVEs (FIRST EPSS, 2026-11-08).
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
-
securityfocus.com
/bid/22496
vdb-entry, patch
-
trustix.org
/errata/2007/0009/
vendor-advisory
-
openpkg.com
/security/advisories/OpenPKG-SA-2007.010.html
vendor-advisory
-
secunia.com
/advisories/24089
third-party-advisory, vendor-advisory
-
osvdb.org
/32768
vdb-entry
- php.net /releases/5_2_1.php
-
secunia.com
/advisories/24419
third-party-advisory
- php.net /ChangeLog-5.php#5.2.1
-
vupen.com
/english/advisories/2007/0546
vdb-entry
Sources
- CVE List CVE-2007-0905
- NVD CVE-2007-0905
Fencer Vulns 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.