Skip to content
Fencer Intel
low 3.3

CVE-2011-1072 json

The installer in PEAR before 1.9.2 allows local users to overwrite arbitrary files via a symlink attack on the package.xml file, related to…

published 2011-03-03 15 y ago modified 2026-06-16 4 mo ago also EUVD-2011-1087

cvss
3.3
version 2.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.5%
EPSS 0.5% chance of exploitation in 30 days, percentile 41%
public exploits
0
none known

Summary

The installer in PEAR before 1.9.2 allows local users to overwrite arbitrary files via a symlink attack on the package.xml file, related to the (1) download_dir, (2) cache_dir, (3) tmp_dir, and (4) pear-build-download directories, a different vulnerability than CVE-2007-2519.

Patch / fix

  • php-pear RHEL 6 1:1.9.4-4.el6

red hat advisories RHSA-2011:1741

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-2011-1072 updated cvss 2.1

php-pear: symlink vulnerability in PEAR installer

  • Red Hat Enterprise Linux Server (v. 6) php-pear 1.9.4-4.el6 Red Hat Enterprise Linux Workstation (v. 6) php-pear 1.9.4-4.el6
    fixed: vendor fix RHSA-2011:1741
  • Red Hat Enterprise Linux 5 php-pear
    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

Exploit prediction

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

Exploits and checks

  • pear.php.net http://pear.php.net/bugs/bug.php?id=18056 referenced PoC, tagged "exploit" by a source, unverified

CVSS scores

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

Classification

Weakness
  • CWE-59 Improper Link Resolution Before File Access

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.