PHP shipped critical fixes this week. Does your AI-built app even run PHP?
PHP patched every supported version on 19 November. Most Lovable, Bolt and v0 apps never touch PHP, but plenty of "AI-built" projects quietly do. Here is how to tell in five minutes.
On Thursday 19 November the PHP project released security updates for every version it still supports: 8.2.36, 8.3.37, 8.4.28 and 8.5.13. The advisory the day before rated the worst of the bugs as critical, and the published list includes several use-after-free and session-handling flaws that can lead to remote code execution under the right conditions.
Two things keep this from being a fire drill. PHP itself says the critical issues "require either non-default configuration or uncommon setups", and none of the reporting we read describes attacks on these new flaws yet. That is different from last month's PHP2Shell bugs, which did see limited exploitation.
Does this reach your app?
If you built with Lovable, Bolt, v0 or Replit's default templates, your front end is JavaScript and your backend is most likely Supabase, a serverless function or a Node server. None of that runs PHP, and there is nothing to patch.
Where PHP sneaks in is the part of the project nobody thinks of as "the app":
- A WordPress or WooCommerce marketing site sitting next to the app on the same domain or host.
- A Laravel or plain PHP API an AI agent scaffolded because you asked for "a backend" on cheap shared hosting.
- A contact form handler or webhook receiver written as a single
.phpfile and uploaded by FTP. - A Docker image built from an old
php:8.xbase tag that nobody has rebuilt since.
The five-minute check
- Search the repo for
.phpfiles, acomposer.json, or aFROM phpline in any Dockerfile. - If you find one, check which version actually runs in production.
php -von the server, the hosting panel, or a response header likeX-Powered-Bywill tell you. - On managed or shared hosting, ask your host when the 19 November release will be installed. On a VPS or your own container, it is yours: update the package or rebuild the image on the new tag.
- If you are on PHP 8.1 or older, this release does not cover you at all. The PHP project no longer ships security fixes for those versions, so the real job is an upgrade, not a patch.
The pattern worth noticing
AI tools are very good at producing a working app and very quiet about what it depends on. A project generated in an afternoon can easily carry three runtimes, two hosts and a forgotten form handler. Knowing your own stack is what turns a headline like this one into either "not us" or a ten-minute fix, instead of a week of wondering.
Quick answers
Do Lovable, Bolt or v0 apps need the PHP update from 19 November 2026?
Usually not. Their front ends are JavaScript and their backends are typically Supabase, serverless functions or Node, none of which run PHP. Only a PHP part you added yourself, such as a WordPress site, a Laravel API or a .php form handler, needs updating.
Which PHP versions fix the November 2026 vulnerabilities?
PHP 8.2.36, 8.3.37, 8.4.28 and 8.5.13, released on 19 November 2026. PHP 8.1 and older no longer receive security fixes from the PHP project, so those need an upgrade rather than a patch.
How do I check whether my project uses PHP?
Search the repository for .php files, a composer.json file or a Dockerfile that starts FROM php. If you find any, run php -v on the server or check your hosting panel to see which version runs in production.
Not sure whether this touches your app? That is exactly what the audit answers.
Book my audit