33
Channel to sync with /r/PHP /r/Laravel /r/Symfony. Powered by awesome @r_channels and @reddit2telegram
I built an open-source way to run Laravel on AWS Lambda Web Functions (FrankenPHP + Octane), and now a hosted dashboard in beta
Hey r/PHP 👋
For the past months I've been working on Arco, an open-source CLI that deploys Laravel to AWS Lambda Web Functions using FrankenPHP + Octane. I've just opened a beta of Arco Cloud, a hosted dashboard on top of it, and I'd love feedback from people who actually run Laravel in production.
# Why Web Functions?
Most serverless Laravel setups use classic, event-based Lambda: API Gateway turns each HTTP request into a JSON event, a runtime translates it for Laravel, and each execution environment handles one request at a time.
Lambda Web Functions are different: the function is an HTTP server.
Requests reach it over HTTP directly. No API Gateway, no event translation.
Each environment handles many concurrent requests (64 by default, up to 128).
With FrankenPHP worker mode, Laravel boots once and serves those requests concurrently.
Native response streaming (SSE works).
Per-endpoint scaling guards (`maxEnvironments`, `rateLimit`) so a traffic spike doesn't melt your database.
In short: fewer environments, fewer cold starts, and a request path that looks like a normal web server.
# What Arco (the open-source CLI) does
arco deploy builds your app and deploys it to your own AWS account
Queues (SQS) with workers and DLQs, storage (S3), cache (DynamoDB), scheduled tasks
Custom domains with SSL, on Route 53 or Cloudflare
Secrets from SSM / Secrets Manager
Tag-based ownership: it refuses to touch AWS resources it didn't create
Optional IAM permissions boundary on the role it creates
--json output (NDJSON) if you want to drive it from your own CI
It's free and open source, and it'll stay that way.
# What Arco Cloud adds (beta)
Connect your AWS account with a CloudFormation template that has scoped permissions and a permissions boundary
git push = deploy, with every step streamed live
Environments, domains, variables and secrets managed from a UI
Arco Runners (early): instead of building in your GitHub Actions, we build on our own Firecracker MicroVMs. There's no workflow file and no secrets in your repo, and each environment keeps a warm VM with vendor/ and node_modules/. In our tests, repeat deploys went from \~2 min (cold) to \~1 min (warm).
Your app, data and AWS bill always stay in your account. Cloud only orchestrates.
# How it compares to Vapor
Same broad idea (Laravel on Lambda in your own account), different foundation: Web Functions + FrankenPHP instead of event-based Lambda behind API Gateway, plus an open-source core you can use without the platform.
# What I'm looking for
People willing to try it on a real (or realistic) app. I'll give free plans to beta testers: just DM me or comment.
Honest feedback: what's missing, what would stop you from using it, what breaks.
Links:
Arco Cloud beta: [https://staging.arcocloud.app](https://staging.arcocloud.app)
Open-source CLI: https://github.com/multi-api/arco
Happy to answer anything about Web Functions, FrankenPHP on Lambda, cold starts, costs, etc.
https://redd.it/1xdrtwi
@r_php
PHP Internals: What Really Happened (w/ Derick Rethans)
https://youtu.be/5X5csEbmHqs?si=vdfccYpnelBTrfbZ
https://redd.it/1xdrk7v
@r_php
CNN article suggested migrating awa from PHP
https://www.cnn.com/2026/10/23/tech/ai-cybersecurity-php2shell-explained
https://redd.it/1xdedqk
@r_php
I backported Sury’s PHP 7.3 php2shell fix (CVE-2026-109618/109619) to Ubuntu 18.04, 20.04 and Debian 10
Sury's 7.3.33-35 fixes php2shell, but he only publishes it for Ubuntu 22.04+ and Debian 11+. If you're stuck on Ubuntu 18 or 20 with PHP 7.3, there's no fixed package.
So I used Opus to help me rebuild his -35 source for Ubuntu 18.04, 20.04 and Debian 10, plus a script that installs it. It checks your server first, backs up your current PHP, then installs the fixed version. Roll back anytime with --restore.
Install guide is on GitHub: https://github.com/Andrew2142/php73-backport
Or run it straight from my DigitalOcean Space:
Ubuntu 18.04:
curl -fsSL https://php73-backport.fra1.digitaloceanspaces.com/install-18.04.sh | sudo bash
Ubuntu 20.04:
curl -fsSL https://php73-backport.fra1.digitaloceanspaces.com/install-20.04.sh | sudo bash
Debian 10:
curl -fsSL https://php73-backport.fra1.digitaloceanspaces.com/install-debian-10.sh | sudo bash
Only covers PHP 7.3 on amd64. It doesn't touch control-panel PHP (cPanel, Plesk etc.). Upgrading off 7.3 is still the real fix; this just buys time.
https://redd.it/1xdbsyy
@r_php
Informational advisory: Session upload progress
https://www.php.net/archive/2026.php#2026-10-23-1
23 Oct 2026
Informational advisory: Session upload progress
We suggest you set session.upload_progress.enabled=0 until the next regular bugfix release, to fully protect from an unlikely RCE vector. This setting was already listed as a mitigation in the GHSA-6wmf-4rv5-p3rp advisory for CVE-2026-109619 published on Oct 21st, 2026. If you applied it then, keep it in place and no further action is needed.
The issue can only occur under an unusual combination of configuration and application code. An application must set session.serialize_handler to php_binary or php_serialize in its configuration and then switch it to php at runtime with ini_set() before calling session_start(). Session upload progress must also still be enabled. Applications that never change the serialize handler at runtime can keep the feature enabled. Since this setup is unlikely in practice, we are handling it in the regular release cycle and will publish a full advisory for CVE-2026-115560 with the next release.
https://redd.it/1xdb9xl
@r_php
SymfonyCon Warsaw 2026: You Are (Not) a Machine
https://symfony.com/blog/symfonycon-warsaw-2026-you-are-not-a-machine?utm_source=Symfony%20Blog%20Feed&utm_medium=feed
https://redd.it/1xdenhn
@r_php
Nice read and so very true
https://theatlantic.com/technology/2026/10/man-who-saved-internet-php-vulnerability/689123/
https://redd.it/1xdbeur
@r_php
If AI tools can independently rediscover a critical PHP bug in a day, can coordinated disclosure embargoes still work?
With the PHP2Shell releases, one detail stood out to me: a security vendor said it independently found the same issue using a frontier model and a basic prompt, within a day of hearing something was coming. Details also leaked before the planned release, and fixed builds went public early.
That raises a broader question for the PHP community, beyond who was right in this specific case:
\- If rediscovery is this cheap, how long can an embargo realistically hold?
\- Should projects plan for shorter embargo windows, or pre-stage patches and packages so distros can ship the same hour?
\- What should happen to the ecosystem around PHP (distros, hosts, Docker images) once a fix is public but not yet packaged?
Curious how maintainers and people running PHP in production see this.
https://redd.it/1xd9amm
@r_php
New in Symfony 8.2: More MongoDB Integrations
https://symfony.com/blog/new-in-symfony-8-2-more-mongodb-integrations?utm_source=Symfony%20Blog%20Feed&utm_medium=feed
https://redd.it/1xd7sjo
@r_php
PHP critical RCE release (8.4.27): what should website owners actually do right now?
I run websites on PHP (WordPress/custom PHP, shared hosting/VPS). I saw the PHP Foundation’s post about the Oct 21 security release (8.4.27) fixing two critical RCE vulnerabilities, with updating as the only fix.
As a website owner, what should I do right now?
a). How do I confirm my server is affected and whether my host has patched it?
b). What’s the safest order: backup, update PHP, then check logs for exploit attempts?
c). Any temporary protection (WAF rules, disabling extensions) until the update is done?
https://redd.it/1xd4k8n
@r_php
Regarding PHP security that were discovered 2 days ago
My question is about the PHP security exploits that were discovered yesterday. I heard the issue was fixed a day ago meaning yesterday. I am not very familiar with cybersecurity and things like that, but as a regular user right now browsing sites like SourceForge and regular websites, is it totally fine for me to use them, browse normally, and download things, or is there still any danger and the issue hasn't been 100% resolved?
https://redd.it/1xd3pm7
@r_php
There are many sites where the administrators stopped performing updates, even after critical issues were discovered in PHP—does that mean those sites will eventually become inaccessible?
I know of many sites that I relied on heavily, but which were abandoned by their administrators long ago. Now, following the recent PHP-related issues, whenever I try to open them, I’m met with warning messages. Are all these sites—and there are so many of them—simply destined to be left behind for good? There are still so many I’d love to keep using :<
https://redd.it/1xd1hqx
@r_php
Unofficial Windows binaries of PHP 7.4, 8.0 and 8.1 with the PHP2Shell fixes (CVE-2026-109618/109619)
php.net announced that the PHP security team published minimal source backports of the PHP2Shell fixes for the end-of-life branches 7.4, 8.0 and 8.1, for people who build from source. There are no official Windows binaries for them, so I built them: https://github.com/Jamalofski/php-eol-security
\- Sources: only the upstream backport commits (last official release plus the fix), no other code change.
\- Build: the official php/php-windows-builder, with the toolchains (vc15/vs16), configure flags and dependencies of the official builds; x64/x86, TS/NTS.
\- Versions: 7.4.33-pl1, 8.0.30-pl1 and 8.1.34-pl1, with SHA256SUMS and a link to the CI run of each build.
These are not official PHP Group binaries. Upgrading to a supported version remains the real fix; this is for setups that cannot move yet.
https://redd.it/1xc1ewu
@r_php
Someone Knew About PHP's Critical Flaws Four Days Before the Public Did and Amazon Can't Explain How
https://www.techtimes.co.uk/amazon-detects-php2shell-exploit-before-disclosure-1809341
https://redd.it/1xcncjf
@r_php
Have Alma turned off Upload progress in the PHP2Shell update?
I just updated PHP on Alma Linux and now upload progress is not working. I have verified it is enabled but the session variable starting "upload_progress_" is never created. There is nothing on their update page suggesting it should have stopped working. This is PHP 7.2 https://almalinux.org/blog/2026-10-21-php2shell-cve-2026-109618-cve-2026-109619/
https://redd.it/1xcexit
@r_php
After the vulnerability is fixed, how far do we go with damage control?
Say you got your servers patched and now you are "safe".
My understanding from the vulnerability is that someone could have perfectly hacked into the system, retrieved db credentials, and call it a day.
Is credentials rotation necessary?
Is there a way to know if the exploit was actually used?
https://redd.it/1xdbsms
@r_php
Unicorn Benefits of Rust/Go Tooling in PHP
https://tomasvotruba.com/blog/unicorn-benefits-rust-go-tooling-in-php
https://redd.it/1xdcch8
@r_php
Laravel versions, PHP versions, and PHP2Shell
I shared this with Shift users earlier this week and thought it might serve as a helpful reference here as it relates to Laravel versions and their supported PHP versions in regards to updating for the PHP2Shell vulnerabilities.
While source patches are available for earlier versions of PHP, the officially supported PHP versions with the PHP2Shell patch are:
| PHP | Minimum version |
|-----|-----------------|
| 8.5 | 8.5.12 |
| 8.4 | 8.4.27 |
| 8.3 | 8.3.36 |
| 8.2 | 8.2.35 |
As that relates to Laravel, Laravel 9.x is the first version to officially support PHP 8.2:
| Laravel | Constraint | PHP 8.2 |
|---------|----------------|---------|
| 6.x | ^7.2.5\|^8.0 | Unproven |
| 7.x | ^7.2.5\|^8.0 | Unproven |
| 8.x | ^7.3\|^8.0 | Unproven |
| 9.x | ^8.0.2 | Proven |
| 10.x | ^8.1 | Proven |
| 11.x | ^8.2 | Proven |
| 12.x | ^8.2 | Proven |
| 13.x | ^8.3 | - |
tl;dr If you have a Laravel application older than 9.x, you need to upgrade Laravel to at least 9.x to be on a supported, patched version of PHP.
Again, you might be able to find a source patch as a stopgap. But then I recommend upgrading.
https://redd.it/1xdloiy
@r_php
Please stop with PHP2Shell, its over, nothing happened!
I know many people are looking for clicks and to feed traffic to their blogs/posts/vlogs/etc.
But please stop with PHP2Shell, its over and nothing happened.
Let the haters hate and lets move on.
---
PS: Nothing happened because a lot of people worked night and day to fix the exploit, to release patches and updated packages. Thank you people, I don't know who you are but you deserve huge thanks.
https://redd.it/1xdh70d
@r_php
Comedy gold created by BBC’s ‘Cyber Correspondent’ Joe Tidy: “I didn’t know PHP existed…” – Watch from minute 4:00
https://www.youtube.com/watch?v=omSYrjCtfD8
https://redd.it/1xddk6y
@r_php
Advisory: We suggest you set session.upload_progress.enabled=0 until the next regular bugfix release
https://www.php.net/index.php#2026-10-23-1
https://redd.it/1xdcm2p
@r_php
your AI-built app is probably fine. the old server next to it might not be (php2shell + node, oct 21)
/r/AIBuildAndLaunch/comments/1xd7e1k/your_aibuilt_app_is_probably_fine_the_old_server/
https://redd.it/1xd7e8f
@r_php
This week's PHP CVEs showed how far behind our old repos are
I work at a small agency and we still look after 14 client sites we built years ago. When the CVEs dropped on Tuesday I spent two nights patching, and 5 of the 14 were still on PHP 7.x. One was on 5.6. Nobody had touched them since launch because nobody was paying for maintenance.
The first night was all bandages. WAF rules to block the multipart stuff, smaller header limits, and hoping. Proper upgrades on the 7.x ones took the rest of the week and we're still not done with the 5.6 one.
What bothers me is that the vulnerabilities were found by AI tooling, so I don't think this is the last one this year. After this we turned on Coderabbit's security scan across all 14 repos, so at least the next problem shows up as a PR instead of a phone call at 1am. It doesn't fix the fact that half of them are on versions nobody wants to touch though.
For people with old client projects, how are you handling maintenance now? Do you charge for it upfront, drop clients who won't pay, or just eat the nights like this one?
https://redd.it/1xd8i2m
@r_php
PHP2Shell - what do we do now?
It is super important to run checks on the servers now while logs still exist and some forensic data is still available. I was a bit surprised to read https://offseq.com/en/research/php2shell-first-48-hours/
Curious what everyone is doing after the exploit? What logs are you checking? What are you locking down.
I, aka Claude, made a small check for my instance. Maybe it will help you check as well? Feel free to change or use as needed. Licensed under our overlord-is-claude license. Aka, WTFPL.
https://gist.github.com/cgsmith/6e09d68027f17ae289cbc9ba2abc3309
https://redd.it/1xd6h6v
@r_php
php and xampp upgrades?
This question is basicly for xampp to
With the current php isue going on
is it possible to update php in a xampp area?, due that the php directory also contains
a huge directory name windowsXamppPhp ,containing a raw version ? (not sure)
or can i just install the content of the zip file in the php directory in the xammp build
if yes, what build do i need ,on php i can see 4 versions
Thnxzs.
Tom.
https://redd.it/1xd2ueh
@r_php
I made a free VS Code extension that fixes your namespaces when you move a PHP file
Move or rename a PHP file in VS Code and the namespace and use lines don't follow. This fixes that. Drag the file or folder, and the namespace, class name and every use line in your project update.
It's a rebuild of PHP Namespace Resolver, so the old commands and settings still work, and the CPU freeze is fixed.
Free and open source. Search "PHP Namespace Mover" in VS Code extensions, or Open VSX if you use Cursor or Windsurf.
https://github.com/lagudafuadtosin/php-namespace-mover
https://redd.it/1xd2uf5
@r_php
What happened to CRUDBooster? I created a community fork to help keep it alive
I’m not sure how many Laravel developers here remember CRUDBooster from around 2019, but it was a pretty popular tool for quickly building admin panels and CRUD applications.
I have several projects built with CRUDBooster, so I was concerned to see that the original project’s maintenance and newer versions have moved in a different direction. For those of us still maintaining older applications, migrating to a completely different version or framework can be a challenge.
I’ve created a community fork here:
👉 https://github.com/vicheanath/crudbooster-contrib
My goal is to help preserve the legacy codebase, keep existing projects maintainable, and explore fixes for compatibility and security issues as PHP and Laravel continue to evolve.
I’ve also seen discussions about newer PHP security vulnerabilities, which makes me wonder how we can keep older CRUDBooster applications safe and usable.
I’d love to hear from the community:
Is anyone still using CRUDBooster in production?
Are you maintaining existing projects built with the older version?
Would a community-maintained fork with security patches, bug fixes, and compatibility updates be useful?
Would anyone be interested in contributing?
I know maintaining an open-source project takes time, and I can’t promise to support every version or fix every issue. But I’d like to see whether there’s enough interest to keep this project useful for developers who still depend on it.
If you have experience with CRUDBooster, I’d love to hear your thoughts!
https://redd.it/1xd01pe
@r_php
And now you get this XKCD comic
https://xkcd.com/2347/
https://redd.it/1xbyqmb
@r_php
PHP2Shell OOM reachability check
https://github.com/offseq/php2shell-poc
https://redd.it/1xcu3nw
@r_php
php2shell: version-checking misses most vulnerable hosts — here's a crash-based checker instead
Quick take after watching the php2shell (CVE-2026-109618/109619) coverage this week: almost every "are you vulnerable?" check I've seen just reads the X-Powered-By version. That's close to useless, because expose_php=Off is the default on a lot of production setups - roughly 4 in 5 PHP servers don't advertise a version at all. So a version check comes back "unknown" or "looks fine" on the exact hosts you most want to know about.
Since the actual bug is a crash primitive (the OOM/longjmp bailout leaving request state half-initialized), I built a checker that triggers it instead of guessing: it sends a crafted multipart probe and only reports VULNERABLE if the engine actually returns the PHP memory-exhaustion fatal error. Banner-independent. Returns FIXED / VULNERABLE / NO SIGNAL (no-signal = it couldn't crash it and the host hid its version, so it won't pretend to know).
One caveat worth repeating: only run it against servers you control. It sends memory-exhaustion probes that can briefly take out a worker.
Checker: https://o3.security/tools/php2shell-scanner
Disclosure: I work at O3 Security and we built this. There's a longer write-up on the mechanism if you want it — the SAPI differences (mod_php is the worst case because it runs shutdown even on a failed request startup), and the genuinely counterintuitive bit where capping memory with RLIMIT_AS as a "mitigation" actually makes the bug *easier* to hit: https://o3.security/blog/php2shell-cve-2026-109618-109619-analysis
Curious if anyone here has seen the version-banner problem bite them in practice — how are you all confirming patch status across a fleet where half the hosts don't report a version?
https://redd.it/1xcih9v
@r_php