Home Plans Products
Tools
Technology Trends Keyword Lists Browser Extensions
Features
Lead Generation Market Analysis Sales Intelligence
Resources
FAQ About Contact Blog
Account
Login Sign up
Home / Blog / PHP 7.2
Security Advisory

PHP 7.2: 79 Critical Vulnerabilities Explained & Fix Guide

📅 June 07, 2026 ·⏱ 5 min read ·🔒 SiteRecipe Security Team
200 websites still running PHP 7.2  → View full list
79
Total
14
Critical
31
High
30
Medium
3
Low

PHP 7.2 reached end-of-life in November 2020, yet approximately 200 websites still run this vulnerable version. Our security research has identified 79 known CVEs affecting PHP 7.2, with 14 classified as critical severity. These vulnerabilities expose your website to remote code execution, memory corruption, and data breaches. This comprehensive guide explains the risks, shows you how to identify if your site is affected, and provides step-by-step instructions to secure your installation.

The most dangerous vulnerabilities in PHP 7.2 include heap buffer overflows in XML-RPC functions, use-after-free errors in EXIF processing, and HTTP stream parsing flaws. Attackers actively exploit these weaknesses to gain unauthorized access to servers, steal sensitive data, and inject malicious code. Many website owners delay upgrading because they fear compatibility issues or lack technical knowledge. However, the security risks of staying on PHP 7.2 far outweigh the effort required to modernize your stack.

What is Php 7.2?

PHP 7.2 is a server-side programming language that powers a large portion of the internet, including WordPress, Drupal, and thousands of custom web applications. Released in November 2016, it was designed to improve performance and introduce modern coding features. However, like all software, PHP receives security updates throughout its lifetime to patch newly discovered vulnerabilities. When a version reaches its end-of-life date, developers stop releasing security patches, leaving all remaining users exposed to known threats.

Thinking of PHP 7.2 like an older car model helps clarify the risk: manufacturers stop releasing safety recalls once a vehicle is discontinued. Similarly, PHP 7.2 no longer receives security updates, meaning any new vulnerabilities discovered will never be patched. The 79 CVEs affecting PHP 7.2 represent security holes that attackers know about and can exploit. Running outdated software is one of the most common ways websites get hacked, yet it's also one of the easiest problems to fix.

Key Vulnerabilities in Php 7.2

79 CVEs found. The most critical are explained below.

CRITICAL CVE-2018-7584 9.8/10 · CVSS v3.0 ⏱ Immediate
HTTP Response Parsing Memory Error

PHP has a flaw in how it reads data from websites. When downloading content from other servers, PHP can accidentally read more memory than intended, potentially exposing sensitive information or causing the website to crash.

Impact: Attackers could steal confidential data from your server's memory or cause your website to stop working unexpectedly.

↗ View on NVD
CRITICAL CVE-2018-12882 9.8/10 · CVSS v3.0 ⏱ Immediate
Photo Metadata Reading Memory Flaw

PHP's photo information reader has a bug where it closes files it shouldn't be closing. If your website processes image uploads or reads photo metadata, attackers can manipulate images to trigger this flaw.

Impact: Your website could crash when processing certain images, or attackers could potentially execute malicious code on your server.

↗ View on NVD
CRITICAL CVE-2014-10074 9.8/10 · CVSS v3.0 ⏱ Immediate
Dangerous File Upload Permission

If you're using Umbraco (a content management system), the system doesn't properly block .php file uploads. This means attackers can upload executable programs disguised as other files.

Impact: Attackers can upload and run harmful code on your server, giving them complete control of your website and data.

↗ View on NVD
CRITICAL CVE-2019-9020 9.8/10 · CVSS v3.0 ⏱ Immediate
XML Data Processing Memory Error

PHP incorrectly handles certain types of XML data, causing it to access invalid memory locations. If your website processes XML feeds or data from external sources, this creates a vulnerability.

Impact: Attackers could crash your website or potentially execute harmful code by sending malformed XML data.

↗ View on NVD
CRITICAL CVE-2019-9021 9.8/10 · CVSS v3.0 ⏱ Immediate
Compressed Package File Reading Flaw

PHP's handling of compressed file packages (PHAR format) reads beyond the intended file boundaries. Attackers can craft malicious package files to exploit this.

Impact: Attackers could read sensitive data from your server's memory or crash your website when processing certain file uploads.

↗ View on NVD
CRITICAL CVE-2019-9023 9.8/10 · CVSS v3.0 ⏱ Immediate
Text Encoding Processing Memory Error

PHP's multibyte text processing has multiple flaws when handling unusual character encoding. Websites that process international text or user input are at risk.

Impact: Attackers could read sensitive information from server memory or crash your website by submitting specially crafted text.

↗ View on NVD

Additional Vulnerabilities (73 more)

Showing first 10 of 73. View all on NVD ↗

CVE IDSeverityScore PublishedDescription
CVE-2019-9641 CRITICAL 9.8 2019-03-09 An issue was discovered in the EXIF component in PHP before 7.1.27, 7.2.x before 7.2.16, and 7.3.x before 7.3.3. There is an uninitialized read in exif_process_IFD_in_TIFF.
CVE-2020-11546 CRITICAL 9.8 2020-07-14 SuperWebMailer 7.21.0.01526 is susceptible to a remote code execution vulnerability in the Language parameter of mailingupgrade.php. An unauthenticated remote attacker can exploit…
CVE-2019-11034 CRITICAL 9.1 2019-04-18 When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.28, 7.2.x below 7.2.17 and 7.3.x below 7.3.4 can be caused to read past allocated buffer in exif_proc…
CVE-2019-11035 CRITICAL 9.1 2019-04-18 When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.28, 7.2.x below 7.2.17 and 7.3.x below 7.3.4 can be caused to read past allocated buffer in exif_iif_…
CVE-2019-11036 CRITICAL 9.1 2019-05-03 When processing certain files, PHP EXIF extension in versions 7.1.x below 7.1.29, 7.2.x below 7.2.18 and 7.3.x below 7.3.5 can be caused to read past allocated buffer in exif_proc…
CVE-2019-11039 CRITICAL 9.1 2019-06-19 Function iconv_mime_decode_headers() in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6 may perform out-of-buffer read due to integer overflow when parsi…
CVE-2019-11040 CRITICAL 9.1 2019-06-19 When PHP EXIF extension is parsing EXIF information from an image, e.g. via exif_read_data() function, in PHP versions 7.1.x below 7.1.30, 7.2.x below 7.2.19 and 7.3.x below 7.3.6…
CVE-2026-40484 CRITICAL 9.1 2026-04-18 ChurchCRM is an open-source church management system. In versions prior to 7.2.0, the database backup restore functionality extracts uploaded archive contents and copies files fro…
CVE-2001-1370 HIGH 10.0 2001-07-21 prepend.php3 in PHPLib before 7.2d, when register_globals is enabled for PHP, allows remote attackers to execute arbitrary scripts via an HTTP request that modifies $_PHPLIB[libdi…
CVE-2018-10549 HIGH 8.8 2018-04-29 An issue was discovered in PHP before 5.6.36, 7.0.x before 7.0.30, 7.1.x before 7.1.17, and 7.2.x before 7.2.5. exif_read_data in ext/exif/exif.c has an out-of-bounds read for cra…
Full Report Available

All 79 CVEs with AI explanations + fix guide

Plain English · Fix recommendations · Instant PDF & HTML download

⬇ Get Full Report
PDF + HTML · Instant download

Is your website running Php 7.2?

Scan your site in 30 seconds. Used by 500+ web agencies.

How to Check If Your Website Is Affected

How to Fix These Vulnerabilities

Conclusion

PHP 7.2's 79 vulnerabilities—especially the 14 critical flaws—pose an unacceptable security risk to your website and your visitors' data. Upgrading to a supported PHP version is the single most important step you can take to protect against active exploitation. The longer you delay, the greater the risk of a successful breach that could compromise customer information, inject malware, or bring your site offline. Most upgrades are seamless and take less than an hour to complete, making the effort minimal compared to the massive security benefit.

Don't let your website remain vulnerable. Use SiteRecipe.com's free security scanner to identify all outdated technologies on your site, get personalized upgrade recommendations, and track your progress toward a secure, modern web presence. Our platform provides clear guidance for each vulnerability, helping you prioritize fixes and implement them confidently. Start your free security audit today and join hundreds of website owners who've already eliminated their PHP 7.2 vulnerabilities.

Frequently Asked Questions

Will upgrading PHP 7.2 break my website?
Most websites upgrade without issues, but compatibility depends on your specific plugins and custom code. That's why testing on a staging environment first is crucial. Modern hosting providers offer automated upgrades with rollback capabilities, and SiteRecipe.com identifies potential compatibility problems before you upgrade.
What's the difference between the critical CVEs listed?
Critical CVEs like CVE-2019-9020 allow remote code execution (attackers run commands on your server), while CVE-2018-12882 enables memory corruption attacks. All critical vulnerabilities require immediate patching because they bypass your site's security entirely and give attackers full control.
Can I just disable vulnerable PHP features instead of upgrading?
Partially—you could disable XML-RPC, PHAR, or EXIF functions if your site doesn't use them. However, this only patches some vulnerabilities and creates ongoing maintenance burden. Upgrading to PHP 8.x is the permanent, recommended solution that eliminates all 79 CVEs while providing performance improvements.
How long does a PHP upgrade typically take?
Most PHP upgrades complete in 15-30 minutes through your hosting control panel with zero downtime. Testing on staging might add 1-2 hours if you discover compatibility issues. SiteRecipe.com helps you skip the troubleshooting by identifying problems before you upgrade.
Is PHP 7.3 safe, or should I jump straight to PHP 8?
PHP 7.3 is safer than 7.2 but also reached end-of-life in December 2021. PHP 7.4 has support until November 2022, while PHP 8.0+ receives updates through 2025+. For maximum security longevity, PHP 8.1 or 8.2 is the best choice for new upgrades.

Generate white-label reports for your clients

Web agencies use SiteRecipe to produce branded PDF security reports in 30 seconds.

DISCLAIMER: This report is based on publicly available CVE data from the National Vulnerability Database (NVD) maintained by NIST. Detection of a technology version does not confirm active exploitation on any specific website. For informational purposes only. SiteRecipe is not responsible for actions taken based on this report. Always consult a qualified security professional.

Source: nvd.nist.gov · Published: June 07, 2026 · SiteRecipe.com