Languages and formats
PHP
Summary
PHP is a server-side programming language that builds web pages on the web server before they reach the browser. Rasmus Lerdorf announced its first version, Personal Home Page Tools, on June 8, 1995. It runs WordPress, Drupal, Joomla and MediaWiki, and as of October 22, 2026 it is used by 69.3% of websites whose server-side language is known.
What PHP is
PHP is a programming language that runs on a web server and builds web pages before they are sent to a visitor. Code that runs this way is called server-side code. The visitor’s browser never sees the PHP itself, only the finished page it produces.
The name is a recursive acronym, which means the first letter stands for the name itself: PHP: Hypertext Preprocessor. It started out meaning something else. The language began in 1995 as Personal Home Page Tools, a small kit written by Rasmus Lerdorf.12
PHP is an interpreted language. A program called the interpreter reads the PHP code and carries it out each time a page is requested, rather than the code being turned into a finished program ahead of time. PHP code can sit right inside an HTML file, between the markers <?php and ?>, which made it easy for people who already wrote web pages to add small bits of logic.1
It is the most common server-side language on the web by a wide margin. As of October 22, 2026, W3Techs counts PHP on 69.3% of websites whose server-side language it can detect.3 The next most common, JavaScript, stood at 8.1% in the same survey as of October 21, 2026. W3Techs notes that one site can use more than one language, so the shares do not add up to 100%.4
Origins: from Personal Home Page Tools to PHP 3
Rasmus Lerdorf created the first version in 1994. According to the PHP project’s own history, it was a set of Common Gateway Interface (CGI) programs written in the C language. CGI is a standard way for a web server to run an outside program and send that program’s output back as a web page. Lerdorf first used the tools to track visits to his online resume.1
On June 8, 1995, Lerdorf announced the kit to the world on Usenet, a worldwide discussion network older than the web, in the group comp.infosystems.www.authoring.cgi. His post opened: “Announcing the Personal Home Page Tools (PHP Tools) version 1.0.”2 The tools logged page visits, showed access counters, password-protected pages, handled forms and offered server-side includes on servers that did not support them.2
Later in 1995 Lerdorf rewrote the code and called it FI, short for Forms Interpreter. It had variables that worked like those in Perl, turned form fields into variables automatically and let authors embed code in HTML. The project’s history describes the syntax as similar to Perl but more limited and somewhat inconsistent.1
The next version, PHP/FI, combined the two names. In 1996 it added built-in support for the DBM, mSQL and Postgres95 databases, cookies and user-defined functions. PHP/FI 2.0 left beta in November 1997, and it was the only full release of PHP 2.0.1
Use grew quickly. The PHP history page cites a Netcraft survey from May 1998 in which nearly 60,000 domains sent web headers containing “PHP”, about 1% of all domains at the time.1
In 1997 two developers from Tel Aviv, Israel, Andi Gutmans and Zeev Suraski, began a complete rewrite of the part of PHP that reads and understands code (the parser). In June 1998 the new PHP Development Team announced PHP 3.0 as the official successor to PHP/FI 2.0. This release gave the language its recursive name.1
PHP 3.0’s main strength, the history page says, was that it was easy to extend. Dozens of developers submitted modules that added new abilities. PHP 3.0 was on more than 70,000 domains when it was announced and, at its peak, on about 10% of web servers.1
Major versions
PHP 4 and the Zend Engine (2000)
Gutmans and Suraski next rewrote PHP’s core. They called the new core the Zend Engine, a blend of their first names, Zeev and Andi. An engine, in this sense, is the part of the interpreter that compiles and runs code. It was first introduced in mid-1999.1 The same year the two founded a company, Zend Technologies.5
PHP 4.0.0, built on the Zend Engine, was released on May 22, 2000.6 A later 4.x release, PHP 4.2.0 on April 22, 2002, changed an important security default that is covered in the security section below.7
PHP 5 (2004)
PHP 5.0.0 arrived on July 13, 2004.8 Its core was Zend Engine II, with a new object model.8 An object model is the set of rules for objects, the bundles of data and functions used in object-oriented programming.
The 5.x series ran for a decade. PHP 5.3 added namespaces (a way to keep names in one library from clashing with names in another), and PHP 5.4 added traits and a short syntax for arrays.1 PHP 5.4.0 shipped on March 1, 2012, and PHP 5.6.0 on August 28, 2014.910
The abandoned PHP 6
The plan for PHP 6 was deep support for Unicode, the standard that lets computers store text in every writing system. The work was later abandoned, and some of its other planned features moved into PHP 5.3 and 5.4.1
A 2014 proposal by Andrea Faulds and Zeev Suraski set out the timeline: the PHP 6 effort began in 2005 and was abandoned in 2010, mainly because of difficulties with the Unicode implementation. Books and articles about the unreleased PHP 6 already existed, so the authors argued that reusing the number would confuse people. Developers voted 58 to 24 in July 2014 to name the next major version PHP 7.11
PHP 7 and the speed jump (2015)
The speed work behind PHP 7 first appeared in May 2014 as an experimental branch called phpng (PHP next generation), which the project said was not ready for production.10 PHP 7.0.0 was released on December 3, 2015.12
The release announcement said PHP 7 was up to twice as fast as PHP 5.6 and used significantly less memory. It came with a new version of the Zend Engine, which the history page calls Zend Engine 3.0.131 Version 7.0 also added return type declarations, scalar type declarations and the null coalescing operator (??), a short way to supply a default value.13
Scalar type declarations let a programmer state that a function expects, for example, an integer or a string. The proposal passed 108 to 48 in March 2015. It included an optional strict mode, switched on per file with declare(strict_types=1), that rejects values of the wrong type instead of silently converting them.14
Later 7.x releases added typed properties and a foreign function interface (a way to call code written in C) in PHP 7.4.1 PHP 7.4.0 was released on November 28, 2019.15
PHP 8 and the JIT (2020)
PHP 8.0.0 was released on November 26, 2020.16 Its headline features were named arguments, union types, attributes (structured notes attached to code), the match expression, the nullsafe operator and a just-in-time compiler, or JIT.17
A JIT turns the most frequently run parts of a program into machine code while the program is running. PHP’s release page reported that the tracing JIT ran about three times faster on synthetic benchmarks and 1.5 to 2 times faster on some long-running applications, while typical web application performance was on par with PHP 7.4.17
The JIT proposal, by Dmitry Stogov and Zeev Suraski, passed 50 to 2 in March 2019. Its own benchmarks showed why ordinary websites saw little change: WordPress served about 326 requests per second with the JIT and 315 without it, while a CPU-heavy fractal benchmark ran more than four times faster.18
PHP 8.1 to 8.5
Since 8.0, PHP has shipped one feature release a year, in late November or early December.19
- PHP 8.1 (November 25, 2021) added enumerations, readonly properties, fibers (a building block for running tasks concurrently) and first-class callable syntax. Its release page reported a 23.0% speedup on the Symfony demo application and 3.5% on WordPress compared with PHP 8.0.2021
- PHP 8.2 (December 8, 2022) added readonly classes and disjunctive normal form (DNF) types, a way to combine type rules.191
- PHP 8.3 (November 23, 2023) added typed class constants.191
- PHP 8.4 (November 21, 2024) added property hooks, asymmetric visibility, a new HTML5-compliant DOM parser and a new JIT implementation.1922
- PHP 8.5 (November 20, 2025) added the pipe operator (|>), a built-in extension for parsing web addresses, “clone with” and the #[\NoDiscard] attribute.1923
PHP 8.6 was in release-candidate testing in October 2026.24
Who makes PHP
PHP is open-source software: its source code is public, and anyone may propose changes. The PHP Group and the project’s contributors hold the copyright in PHP’s code. Zend Technologies, now a subsidiary of Perforce Software, holds copyright in parts of the Zend Engine.25
How changes are decided
Changes to the language go through a public process. Anyone with a proposal writes a Request for Comments (RFC) on the PHP wiki, it is discussed on the developers’ mailing list, and then it is put to a vote.26
The voting rules were adopted in 2011, in a proposal by Zeev Suraski, Pierre Joye and David Soria Parra. Accepting a proposal needs a two-thirds majority. Voters are people with php.net accounts who have contributed code, plus community representatives such as lead developers of major PHP projects.26
Zend
Zend Technologies, founded by Gutmans and Suraski in 1999, sold commercial PHP products and released Zend Framework in 2006. Rogue Wave Software bought Zend in 2015, and Perforce Software bought Rogue Wave in 2019. Zend now sells PHP builds with support that runs past the community’s end-of-life dates.5
The PHP Foundation
The PHP Foundation was announced on November 22, 2021, as a body to fund work on the PHP language.20 According to JetBrains, which helped set it up, the trigger was that Nikita Popov, one of PHP’s most active core developers, was leaving JetBrains on December 1, 2021 and would spend much less time on PHP. Too much knowledge sat with too few people.27
The foundation was organized as a nonprofit through Open Collective, a platform that handles money and paperwork for open-source groups. JetBrains planned to give $100,000 a year, and the initial target was about $300,000 a year from all sponsors, mainly to pay core developers.27
In February 2026 the foundation named Elizabeth Barron as executive director. She succeeded founding executive director Roman Pronskiy.28 In May 2026 it created an Ecosystem Security Team, funded by a grant from Alpha-Omega, a security program tied to the Linux Foundation and the Open Source Security Foundation.29
License
An open-source license is the legal permission that lets anyone use, change and share software. For most of its history PHP used its own PHP License 3.01, with a separate Zend Engine License. A 2025 proposal by Ben Ramsey to switch both to the Modified BSD License (known as BSD-3-Clause) passed 51 to 0, with 2 abstentions.30 As of October 2026, php.net says PHP is available under the Modified BSD License, also called the PHP License, version 4, starting with PHP 8.6. Users of earlier versions may also choose it.25
The LAMP stack and software built on PHP
A software stack is a set of programs that work together to run a website. The best-known stack of the early web was LAMP: Linux (the operating system), Apache (the web server), MySQL (the database) and a scripting language starting with P, usually PHP, Perl or Python.31
According to Computerworld, the writer Michael Kunze coined the acronym in December 1998 in the German computing magazine Computertechnik, to show that free software could replace expensive commercial packages. The publisher O’Reilly and the company behind MySQL later helped spread the term.31
The same basic recipe still runs much of the web. WordPress.org recommends hosting with PHP 8.3 or newer, MySQL 8.0 or MariaDB 10.11 or newer, HTTPS support, and either Apache or Nginx as the web server.32
Applications written in PHP
A content management system (CMS) is software for publishing and editing a website without writing code for each page. The most widely used ones are written in PHP.
- WordPress is used by 39.6% of all websites and holds 58.3% of the market among sites whose CMS W3Techs can identify, as of October 22, 2026.33
- Drupal 11 supports PHP 8.3 and 8.4, and PHP 8.5 from version 11.3, and Drupal 10 requires at least PHP 8.1.34
- Joomla describes itself as a free, open-source CMS based on PHP and MySQL.35
- MediaWiki, the wiki software, states that PHP is the language it is written in and that PHP is required to run it.36
A framework is a ready-made foundation of code that developers build custom applications on. Laravel is a PHP framework whose version 12 supports PHP 8.2 to 8.5 and whose version 13 supports PHP 8.3 to 8.5.37 Symfony is both a PHP framework and a set of reusable PHP packages, which, according to Symfony, are used by Drupal, PrestaShop and Laravel.38
Facebook, HipHop and HHVM
Facebook’s website was written in PHP. In February 2010 its engineers released HipHop for PHP, a tool that converted PHP code into C++ so it would run faster. Facebook said the site served more than 400 billion PHP-based page views a month and that HipHop cut CPU use on its web servers by about 50% on average.39
HipHop was followed by HHVM, a virtual machine that ran both PHP and Facebook’s own PHP-derived language, Hack. In September 2018 the HHVM team announced that version 3.30 would be the last to aim for PHP support, and that later versions would focus on Hack.40
Security record
Because so many sites run PHP, flaws in PHP itself matter widely. This section covers flaws in PHP itself and in its default settings, not flaws in the applications built with it.
register_globals
In early PHP, values from outside a script, such as fields in a web address, form data, cookies and server settings, were turned into ordinary global variables by default. This setting was known as register_globals. So a value sent with a request could turn up as a variable inside the script.
PHP 4.2.0, released in April 2002, changed the default so that outside values were no longer registered as global variables. The project recommended that code read them from special arrays called superglobals, introduced in PHP 4.1.0.417 PHP 5.4.0 removed register_globals completely, along with two other old features, magic quotes and safe mode.42
Notable vulnerabilities
A vulnerability is a flaw that an attacker can use to make software do something it should not. Each publicly known one gets an ID from the CVE (Common Vulnerabilities and Exposures) program.
- CVE-2012-1823. In May 2012, PHP fixed a flaw in setups that run PHP as a CGI program, which it said had gone unnoticed for at least eight years. Apache with mod_php and Nginx with PHP-FPM were not affected.9 The U.S. National Vulnerability Database shows a CVSS 3.1 severity score of 9.8 out of 10 for it, supplied by CISA, and the U.S. Cybersecurity and Infrastructure Security Agency (CISA) added it to its catalog of exploited vulnerabilities in March 2022.43
- CVE-2024-4577. The security firm DEVCORE found that a Windows character-conversion feature could bypass the 2012 fix. DEVCORE reported it on May 7, 2024, and PHP fixed it on June 6, 2024, in versions 8.3.8, 8.2.20 and 8.1.29.4445 PHP’s advisory, which credits DEVCORE researcher Orange Tsai, says an attacker could run any PHP code on an affected Windows server.46
- PHP2Shell (2026). On October 21, 2026, PHP released 8.5.12, 8.4.27, 8.3.36 and 8.2.35 to fix two critical flaws, CVE-2026-109618 and CVE-2026-109619, that could let an attacker run code on a web server without logging in.47 Researchers at Wiz, who published the flaws under the name PHP2Shell, said every PHP version released in the previous decade, back to PHP 5.4, had at least one of them.48
Attacks on the project itself
In March 2021, two malicious changes were pushed into PHP’s source code under the names of Rasmus Lerdorf and Nikita Popov. Popov wrote that everything pointed to a break-in at the project’s own git.php.net server. The project shut that server down and made its copies on GitHub the official ones, with two-factor authentication required for anyone who can make changes.49
Audits and the security team
In 2024 the security firm Quarkslab audited the most critical parts of PHP’s source code. The audit was organized by the Open Source Technology Improvement Fund and paid for by Germany’s Sovereign Tech Agency. It found 27 issues, 17 with security implications, 3 of them rated high.5051
The PHP Foundation later said that, while fixing an issue from that audit, a core developer found the first signs of the memory problem behind PHP2Shell, and that the fix then stalled for months because the security team worked by consensus and could not agree on an approach. It called the delay “a structural failure” and said it had begun changing its processes so decisions can be made by majority.51
Version support
Each PHP branch (for example 8.4) gets two years of active support, with regular bug and security fixes, and then two more years of fixes for critical security issues only. After four years the branch reaches end of life and gets no more updates from the PHP project.19 The dates below come from php.net’s supported-versions and end-of-life pages and the release announcements cited above.1952
| Branch | First released | Active support ends | Security fixes end | Status, Oct 22, 2026 |
|---|---|---|---|---|
| 8.5 | Nov 20, 2025 | Dec 31, 2027 | Dec 31, 2029 | Active support |
| 8.4 | Nov 21, 2024 | Dec 31, 2026 | Dec 31, 2028 | Active support |
| 8.3 | Nov 23, 2023 | Dec 31, 2025 | Dec 31, 2027 | Security fixes only |
| 8.2 | Dec 8, 2022 | Dec 31, 2024 | Dec 31, 2026 | Security fixes only |
| 8.1 | Nov 25, 2021 | Ended | Dec 31, 2025 | End of life |
| 8.0 | Nov 26, 2020 | Ended | Nov 26, 2023 | End of life |
| 7.4 | Nov 28, 2019 | Ended | Nov 28, 2022 | End of life |
| 7.0 | Dec 3, 2015 | Ended | Jan 10, 2019 | End of life |
| 5.6 | Aug 28, 2014 | Ended | Dec 31, 2018 | End of life |
Many sites run older branches. Among websites that use PHP, W3Techs counts 65.3% on PHP 8, 26.9% on PHP 7, 7.7% on PHP 5 and 0.1% on PHP 4, as of October 22, 2026.3 None of the PHP 7, 5 or 4 branches get fixes from the PHP project, and neither do PHP 8.0 and 8.1.52
An end-of-life branch is not always unpatched. Linux distributions and long-term support (LTS) vendors often copy fixes back into older versions they still ship, a practice called backporting.47 Zend also sells PHP builds with support beyond the community schedule.5 For PHP2Shell, the PHP security team itself published minimal fixes for PHP 7.4, 8.0 and 8.1 because the flaws were so severe.47
Criticism and defenses
PHP has been criticized for as long as it has been popular. The arguments are worth knowing because they shaped how the language changed.
Design
The best-known critique is a 2012 essay by the programmer Eevee titled “PHP: a fractal of bad design.” It argued that PHP’s built-in functions are named and ordered inconsistently, that its loose comparison operator (==) converts types in surprising ways, and that errors are too easy to miss.53 PHP’s own history page describes the syntax of the 1995 version as “somewhat inconsistent.”1
Defenders point to how much the language has changed since then: optional strict typing in 2015, typed properties in 7.4, and union types, enumerations and readonly classes in the 8.x series.141
Results versus elegance
In 2008, the programmer Jeff Atwood, who called PHP badly designed, argued that it mattered less than people thought, because many large and successful sites had been built with it.54 Facebook’s engineers, for example, said they valued PHP because it let them move fast, even as they built tools to work around its speed limits.39
Speed
Speed was a known weakness: Facebook built HipHop because, its engineers wrote, C++ far outperforms PHP in processor and memory use.39 PHP 7 was then announced as up to twice as fast as PHP 5.6.13 The JIT added in PHP 8.0 helps CPU-heavy code far more than typical websites.18
Security and process
Critics have pointed to unsafe defaults such as register_globals, which PHP turned off by default in 2002 and removed in 2012.4142 The handling of PHP2Shell drew criticism from inside the project itself: the PHP Foundation said the fix for the underlying bug had stalled for months.51 Supporters note that the project now pays for outside audits and full-time security engineers through the foundation.5029
PHP today
As of October 22, 2026, four PHP branches get updates from the PHP project: 8.2, 8.3, 8.4 and 8.5. PHP 8.2’s security support ends on December 31, 2026, and PHP 8.4’s active support ends the same day.19 The newest release in each branch is 8.5.12, 8.4.27, 8.3.36 and 8.2.35, all published on October 21, 2026 to fix PHP2Shell.47
WordPress, the most used CMS, requires PHP, and the language’s share of the web, 69.3% of sites with a known server-side language, is far ahead of any other language W3Techs tracks.3334
The number of security reports has grown. The PHP Foundation said in October 2026 that the PHP security team had published 15 CVEs since July 1 and had handled more than 100 reports that turned out to be invalid, duplicates or impossible to reproduce. The foundation linked the higher volume to AI-assisted research. The foundation said AI helps sort reports, but a person makes every decision and works on every fix.51
Timeline
- PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix the PHP2Shell flaws47
- The PHP Foundation creates an Ecosystem Security Team29
- PHP 8.5 is released, with the pipe operator19
- PHP 8.4 is released, with property hooks19
- PHP 8.1 is released, with enumerations and fibers20
- The PHP Foundation is announced to fund PHP development20
- After malicious commits, PHP moves its official code to GitHub49
- PHP 8.0 is released, with a JIT compiler16
- PHP 7.0 is released, up to twice as fast as PHP 5.612
- Developers vote 58 to 24 to skip PHP 6 and name the next version PHP 711
- PHP 5.4.0 removes register_globals, magic quotes and safe mode42
- PHP 5.0.0 is released with Zend Engine II8
- PHP 4.2.0 stops registering request values as global variables by default41
- PHP 4.0.0 is released on the new Zend Engine6
- PHP 3.0, rewritten by Andi Gutmans and Zeev Suraski, is announced1
- PHP/FI 2.0 leaves beta1
- Rasmus Lerdorf announces Personal Home Page Tools on Usenet2
What it means for your website
Most website owners never touch PHP directly, but almost every self-hosted CMS depends on it.
- On a hosted builder such as Squarespace, Wix or Shopify, the platform runs the servers. There is no PHP version for you to manage.
- On self-hosted WordPress, Drupal or Joomla, your web host or developer chooses the PHP version. Aim for a branch that still gets security fixes: 8.2 to 8.5 as of October 2026, with 8.2 ending on December 31, 2026.19 WordPress.org recommends PHP 8.3 or newer.32
- Check your version. In WordPress, go to Tools, then Site Health. The Status tab flags an outdated PHP version as a critical issue, and the Info tab lists server and PHP details.55
- Ask about backports. If your host runs an older PHP version, ask whether it gets security fixes from a Linux distribution or a support vendor.47 If the answer is no, plan an upgrade and test your theme and plugins on a copy of the site first.
- Act fast on critical PHP releases. PHP2Shell showed that a flaw in PHP itself can affect every site on a server, whatever CMS it runs.47 Our news story on PHP2Shell has the steps.
We build on WordPress every week, and the PHP version is one of the first things we check on any site we take over. It is part of the upkeep that comes with self-hosting, which we weigh against hosted builders in our builder vs WordPress vs agency guide and our WordPress review.
See also
- Rasmus Lerdorf (coming soon)
- PHP2Shell (2026)
- WordPress
- MySQL (coming soon)
- Apache HTTP Server (coming soon)
- WordPress review
- Web hosting
- Cms
References
- History of PHP. The PHP Documentation Group, php.net. accessed October 22, 2026.
- Announce: Personal Home Page Tools (PHP Tools). Rasmus Lerdorf, Usenet group comp.infosystems.www.authoring.cgi, via Google Groups. 1995-06-08. accessed October 22, 2026.
- Usage statistics and market share of PHP for websites. W3Techs. 2026-10-22. accessed October 22, 2026.
- Usage statistics of server-side programming languages for websites. W3Techs. 2026-10-21. accessed October 22, 2026.
- About Zend. Zend by Perforce. accessed October 22, 2026.
- PHP news archive, 2000 (PHP 4.0.0 Released). The PHP Group. 2000-05-22. accessed October 22, 2026.
- PHP news archive, 2002 (PHP 4.2.0 released). The PHP Group. 2002-04-22. accessed October 22, 2026.
- PHP news archive, 2004 (PHP 5.0.0 Released). The PHP Group. 2004-07-13. accessed October 22, 2026.
- PHP news archive, 2012. The PHP Group. 2012. accessed October 22, 2026.
- PHP news archive, 2014. The PHP Group. 2014. accessed October 22, 2026.
- PHP RFC: Name of Next Release of PHP. Andrea Faulds and Zeev Suraski, PHP wiki. 2014-07-05. accessed October 22, 2026.
- PHP news archive, 2015 (PHP 7.0.0 Released). The PHP Group. 2015-12-03. accessed October 22, 2026.
- PHP 7.0.0 Release Announcement. The PHP Group. 2015-12-03. accessed October 22, 2026.
- PHP RFC: Scalar Type Declarations (version 0.5). Anthony Ferrara and Andrea Faulds, PHP wiki. 2015-02-18. accessed October 22, 2026.
- PHP 7 ChangeLog. The PHP Group. accessed October 22, 2026.
- PHP news archive, 2020 (PHP 8.0.0 Released). The PHP Group. 2020-11-26. accessed October 22, 2026.
- PHP 8.0 release page. The PHP Group. 2020-11-26. accessed October 22, 2026.
- PHP RFC: JIT. Dmitry Stogov and Zeev Suraski, PHP wiki. 2019-01-28. accessed October 22, 2026.
- Supported Versions. The PHP Group. accessed October 22, 2026.
- PHP news archive, 2021. The PHP Group. 2021. accessed October 22, 2026.
- PHP 8.1 release page. The PHP Group. 2021-11-25. accessed October 22, 2026.
- PHP 8.4 release page. The PHP Group. 2024-11-21. accessed October 22, 2026.
- PHP 8.5 release page. The PHP Group. 2025-11-20. accessed October 22, 2026.
- PHP news archive, 2026. The PHP Group. 2026. accessed October 22, 2026.
- PHP Licensing. The PHP Group. accessed October 22, 2026.
- Request for Comments: Voting on PHP features. Zeev Suraski, Pierre Joye and David Soria Parra, PHP wiki. 2011-06-05. accessed October 22, 2026.
- The PHP Foundation. JetBrains PhpStorm blog. 2021-11-22. accessed October 22, 2026.
- Welcoming Elizabeth Barron as the New Executive Director of The PHP Foundation. The PHP Foundation. 2026-02-27. accessed October 22, 2026.
- Announcing the Ecosystem Security Team at The PHP Foundation. The PHP Foundation. 2026-05-18. accessed October 22, 2026.
- PHP RFC: PHP License Update. Ben Ramsey, PHP wiki. 2025-07-10. accessed October 22, 2026.
- LAMP. Russell Kay, Computerworld. 2006-09-25. accessed October 22, 2026.
- Requirements. WordPress.org. accessed October 22, 2026.
- Usage statistics and market share of WordPress. W3Techs. 2026-10-22. accessed October 22, 2026.
- PHP requirements. Drupal.org. accessed October 22, 2026.
- What is Joomla. Joomla project. accessed October 22, 2026.
- Manual:Installation requirements. MediaWiki.org. accessed October 22, 2026.
- Release Notes, Laravel 12.x. Laravel. accessed October 22, 2026.
- What is Symfony. Symfony. accessed October 22, 2026.
- HipHop for PHP: Move Fast. Haiping Zhao, Facebook Engineering. 2010-02-02. accessed October 22, 2026.
- Ending PHP Support, and The Future Of Hack. Fred Emmott, HHVM blog. 2018-09-12. accessed October 22, 2026.
- PHP 4.2.0 Release Announcement. The PHP Group. 2002. accessed October 22, 2026.
- PHP 5.4.0 Release Announcement. The PHP Group. 2012-03-01. accessed October 22, 2026.
- CVE-2012-1823 Detail. National Vulnerability Database, NIST. accessed October 22, 2026.
- Security Alert: CVE-2024-4577, PHP CGI Argument Injection Vulnerability. DEVCORE. 2024-06-06. accessed October 22, 2026.
- PHP news archive, 2024. The PHP Group. 2024. accessed October 22, 2026.
- PHP RCE: A Bypass of CVE-2012-1823, Argument Injection in PHP-CGI (GHSA-3qgc-jrrr-25jv). PHP project on GitHub. accessed October 22, 2026.
- Security advisory: Critical remote code execution vulnerabilities, update now. The PHP Group. 2026-10-21. accessed October 22, 2026.
- PHP2Shell. Wiz Research (Sagi Tzadik, Shir Tamari, Nir Ohfeld and Tomer Schwartz). 2026-10-21. accessed October 22, 2026.
- Changes to Git commit workflow. Nikita Popov, php.internals mailing list. 2021-03-28. accessed October 22, 2026.
- PHP Core Security Audit Results. The PHP Foundation. 2025-04-10. accessed October 22, 2026.
- Today's PHP Security Release, and How We're Strengthening PHP Security. The PHP Foundation. 2026-10-21. accessed October 22, 2026.
- Unsupported Branches. The PHP Group. accessed October 22, 2026.
- PHP: a fractal of bad design. Eevee, fuzzy notepad. 2012-04-09. accessed October 22, 2026.
- PHP Sucks, But It Doesn't Matter. Jeff Atwood, Coding Horror. 2008-05-20. accessed October 22, 2026.
- Site Health Screen. WordPress.org Documentation. accessed October 22, 2026.
Web Building Encyclopedia. First published October 22, 2026. Last reviewed October 22, 2026. Every fact on this page is linked to a source we opened. Spotted an error? Write to [email protected].