Composer 2.11 is out 🚀 cooldown dependency policies hold back freshly published package versions for an hour or a day, so compromised releases can be flagged before they reach your composer update. https://t.co/IsrRN6TmIL #php#phpc#composerphp#supplychainsecurity
Lot of #PHP snark going around right now from folks who've either never written software, or never done it in PHP (in the last 20 years).
I've architected, designed and hand-coded copious amounts of software in Java/Spring/Hibernate, .Net/C# Entity Framework and PHP/Symfony/Doctrine, applying very similar patterns and better practices of completely stack-agnostic concepts such as:
- Test-Driven Development (and given half-day and full-day hands-on live-coding workshops at conferences worldwide)
- Onion/Hexagonal Architecture
- Domain-Driven Design
- Data Mapper ORMs
Beyond workshops, I have spoken on these topics at conferences worldwide as well.
I might argue that I am not completely devoid of clue when it comes to these stacks' capabilities.
In fact, I have hired, coached and cross-trained engineers across these 3 stacks.
And I can assure you PHP shines within these paradigms, with an extremely vibrant, mature and robust ecosystem of Application Frameworks, Security Frameworks and Tools, and Open-Source Software Components and Libraries.
PHP is not WordPress. WordPress is not PHP. If you care about quality software, PHP is a great home for you. So is Java. So is C#. So are other languages. If you suck at software you'll suck in any stack. If you're good, each stack has strengths you can play to.
NOW let's talk about security.
This vulnerability, is the very first RCE to this level in PHP's history. It was reported back in August. AI did help. A lot. (Wiz claims one researcher did in a week what would previously have taken a team months)
Previous PHP RCEs had limited attack surfaces:
- 2024 - Windows CGI Only
- 2019 - One specific nginx setup
- 2012 - CGI only
None of which applied to reasonably-better practice typical Linux + Nginx + php-fpm deployments.
This right here was ... unique, I think even across any stack. The only language-runtime equivalent to it was probably Windows IIS Code Red.
That's not to say other stacks didn't have framework-level vulnerabilities with devastating impacts, if memory needs refreshed:
Ruby — Rails CVE-2013-0156: every Rails app, default config, pre-controller, botnet-exploited. The strongest analogue in any stack.
Java — Struts 2 CVE-2017-5638 (Equifax). Log4Shell needed the app to log attacker input; Spring4Shell needed WAR-on-Tomcat + JDK 9+ + POJO binding.
Node — React2Shell CVE-2025-55182 (Dec 2025, CVSS 10, CISA KEV): default create-next-app exploitable, but Express/Fastify/Nest untouched.
.NET — MS10-070 padding oracle (2010) leaked web.config/machineKey on every ASP (dot NET) site; RCE was a derived second step. Kestrel/ASP.NET Core has never had an RCE.
Look ... let's drop the snark. LLM-driven vulnerability research and breaching frameworks are about to humble the absolute heck out of all of us. They already have.
If you think your stack is not at risk, think again.
If all the govs shutting down servers for a PHP update, all the hosters & enterprises terrified by the vuln, gave $100k, or just $50k a year to the PHP Foundation, things could look very differently. Go, make your employer sponsor *today* https://t.co/z1mUcXMqy9 #php #phpc @Th@ThePHPF
Our deploy pipeline never sleeps! Here are all the improvements to Private Packagist of the last months: We added support for PIE, streamlined our GitHub sync, made it easier to track setup progress, more on our blog: https://t.co/dnuK01QZCJ #composerphp#composer#php#phpc
Feels like ages to bootstrap a full app.
Even with symfony flex, symfony standard edition, teamcity build templates, ...
And it isnt event deployed yet. waaaah.
How do you let your customers do checkout?
Everyone with an webshop probably has one, but what about SaaS. Yes, you can use Stripe checkout, but feel like this doesnt work well for german business + customers.
So what did you do to solve this?
#ecommerce#saas#buildinpublic
Dont add another boolean to the end of your method that has a default to false ^^ and "completely" changes what the method does.
Just create two methods...
@fabiangruss lol :D
nah, it would be to constantly import invoices created in stripe (we wouldnt use lexoffice to generate invoices, but only for the tax reporting, EÜR, USTVA, etc)
What app do you use for your accounting of your on SaaS? (in germany)
We need to file expenses and import invoices from stripe.
Those are the ones I already know:
Lexware Office (Lexoffice)
Papierkram
Buchhaltungsbuttler
https://t.co/uXZP79zrq1
sevdesk
fastbill
Wiso mein Büro
@SebastianRoehl @devj3ns don't make it a setting :)
One of the versions provides value, the other not so much, or it doesnt matter.
Too big setting-screens are just bloating your product and your code as well?
@chrisgleitze just show them the IBAN and the reference text they should use.
Extra points for creating a payment QR code that they can scan :) to pay by wire transfer.
Although this might only fit b2c in germany. The swiss people wanted to pay by cc :)
@chrisgleitze I would recommend german SaaS to not use any payment provider at all :D
Just automate how you will map bank transfers to invoices and be done.
The germans like to pay via wiretransfer and that's it.
Maybe integrate paypal or google pay later and be done
@chrisgleitze we use stripe. Currently for both:
subscription / invoices / payment processing.
The payment processing part is fine i guess. The invoicing part is mostly okay, but has already some quirks.
Stripe subscriptions are the worst piece of software we have running production 💯
Excited to finally get more than the first handful of customers to use Conductor. It's already been so much fun getting PRs from Conductor ourselves. Been working on this idea on & off for years, finally got it right. Sign up for the early access waitlist!