Skip to content
Fencer Intel
medium 5.0

CVE-2010-1130 json

session.c in the session extension in PHP before 5.2.13, and 5.3.1, does not properly interpret ; (semicolon) characters in the argument to…

published 16y ago modified 4mo ago also EUVD-2010-1161

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

Summary

session.c in the session extension in PHP before 5.2.13, and 5.3.1, does not properly interpret ; (semicolon) characters in the argument to the session_save_path function, which allows context-dependent attackers to bypass open_basedir and safe_mode restrictions via an argument that contains multiple ; characters in conjunction with a .. (dot dot).

Patch / fix

Is CVE-2010-1130 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 Fencer

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-2010-1130 updated

php: safe_mode / open_basedir security fixes in 5.2.13/5.3.2

  • 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-33625)
  2. Published

Exploit prediction

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

Exploits and checks

  • EDB-33625 PHP 5.3.1 - 'session_save_path() Safe_mode()' Restriction Bypass Exploiot dos, 2010-02-11
  • securityreason.com http://securityreason.com/securityalert/7008 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

assigned by version score vector
NVD 2.0 5.0 AV:N/AC:L/Au:N/C:N/I:P/A:N

Classification

Weakness
  • CWE-264 Permissions, Privileges, and Access Controls
Technology feeds

References

Sources

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.