Skip to content
Fencer Vulns
high 7.5

CVE-2007-1376 in the critical feed json

The shmop functions in PHP before 4.4.5, and before 5.2.1 in the 5.x series, do not verify that their arguments correspond to a shmop resou…

published 2007-03-10 19 y ago modified 2026-06-16 4 mo ago also EUVD-2007-1372

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

Summary

The shmop functions in PHP before 4.4.5, and before 5.2.1 in the 5.x series, do not verify that their arguments correspond to a shmop resource, which allows context-dependent attackers to read and write arbitrary memory locations via arguments associated with an inappropriate resource, as demonstrated by a GD Image resource.

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

php shmop argument validation

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

Exploit prediction

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

Exploits and checks

  • EDB-3427 PHP < 4.4.5/5.2.1 - 'shmop' SSL RSA Private-Key Disclosure local, 2007-03-07
  • EDB-3426 PHP < 4.4.5/5.2.1 - 'shmop' Local Code Execution local, 2007-03-07
  • securityfocus.com http://www.securityfocus.com/bid/22862 referenced PoC, tagged "exploit" by a source, unverified
  • php-security.org http://www.php-security.org/MOPB/MOPB-15-2007.html 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.