PHP powers the majority of the public web — WordPress alone is a third of it — and its ecosystem still teaches habits the rest of the industry retired a decade ago. The language grew up; the community's defaults didn't.
The tutorials are the attack surface
Search "PHP file upload" or "PHP login system" and the top results concatenate strings into SQL, store passwords unsalted, and echo user input unescaped. These aren't fringe resources — they're the highest-ranking answers, and they've been copied into production for twenty years. Every language has bad tutorials. PHP's problem is the bad ones still rank first.
Legacy code never retires
The deployment model — FTP a file to a shared host — means code from 2008 still runs today, unpatched, behind domains nobody remembers administering. Composer and modern frameworks exist, but the installed base is old WordPress, old plugins, and unmaintained themes. PHP the language improved; PHP the deployed corpus is a museum.
What modern PHP actually looks like
PHP 8 is a different language: typed properties, enums, fibers, a JIT. Laravel, Symfony and composer-era tooling are professional. The distance between "PHP as written in 2010 tutorials" and "PHP as written now" is wider than the distance between Python 2 and 3 — and the community hasn't enforced the upgrade.
When it breaks
The failure mode is a plugin. One unmaintained WordPress plugin with an XSS or an unpatched file upload is the standard breach story. Audit plugins like dependencies — check the last commit date, the CVE feed, the install count trend — or the ecosystem audits you.
$ tail -f /forums
Discussion
Comments live on the community forums — sign in there to reply.