Skip to content
Fencer Vulns
high 7.5

CVE-2007-1700 json

The session extension in PHP 4 before 4.4.5, and PHP 5 before 5.2.1, calculates the reference count for the session variables without consi…

published 2007-03-27 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1694

cvss
7.5
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
9.1%
EPSS 9.1% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

The session extension in PHP 4 before 4.4.5, and PHP 5 before 5.2.1, calculates the reference count for the session variables without considering the internal pointer from the session globals, which allows context-dependent attackers to execute arbitrary code via a crafted string in the session_register after unsetting HTTP_SESSION_VARS and _SESSION, which destroys the session data Hashtable.

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-1700 updated

php session extension refcount handling issue

  • Red Hat All currently supported Red Hat products
    not 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

Timeline

  1. First public exploit (EDB-3571)
  2. Published

Exploit prediction

9.14% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-08).

Exploits and checks

  • EDB-3571 PHP < 4.4.5/5.2.1 - '_SESSION unset()' Local Overflow local, 2007-03-25
  • securityfocus.com http://www.securityfocus.com/bid/23119 referenced PoC, tagged "exploit" by a source, unverified

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

Sources

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.