CVE-2014-3515

CVE-2014-3515 is a high-severity vulnerability in Php with a CVSS 2.0 base score of 7.5. Its EPSS exploit-prediction score of 30% places it in the 98th percentile, indicating an elevated likelihood of exploitation.

Key facts

Description

The SPL component in PHP before 5.4.30 and 5.5.x before 5.5.14 incorrectly anticipates that certain data structures will have the array data type after unserialization, which allows remote attackers to execute arbitrary code via a crafted string that triggers use of a Hashtable destructor, related to "type confusion" issues in (1) ArrayObject and (2) SPLObjectStorage.

Frequently asked questions

What is CVE-2014-3515?
The SPL component in PHP before 5.4.30 and 5.5.x before 5.5.14 incorrectly anticipates that certain data structures will have the array data type after unserialization, which allows remote attackers to execute arbitrary code via a crafted string that triggers use of a Hashtable destructor, related to "type confusion" issues in (1) ArrayObject and (2) SPLObjectStorage.
How severe is CVE-2014-3515?
CVE-2014-3515 has a CVSS 2.0 base score of 7.5, rated high severity.
Is CVE-2014-3515 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 30% (98th percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2014-3515?
CVE-2014-3515 primarily affects Php. In total, 3 product configurations (CPEs) are listed as vulnerable; see the affected-products list for the exact versions.
How do I fix CVE-2014-3515?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2014-3515 published?
CVE-2014-3515 was published on 2014-07-09 and last updated on 2026-06-17.

References

Affected products (3)

More vulnerabilities in Php

All CVEs affecting Php →

Threat intelligence

Threat-intel indicators referencing this CVE: