This year, security stopped being a once-in-a-while topic for us - it's been our focus. We fixed & published nine CVEs in Backpack...
This year, security stopped being a once-in-a-while topic for us - it's been our focus. We fixed & published nine CVEs in Backpack CRUD, with 9 more on the way (fixed but unpublished), which is more than all other 9 other years combined.
We were a bit down 5 months ago, because one vulnerability had severity 8.1 (High) - our top score so far. Then came October... and in a single month, Linux, PHP and Laravel each shipped much bigger security fixes of their own. We had already hardeden our security by then, but October 2026 made it crystal-clear that the game has changed, and it's more important than ever to keep your stack up-to-date. And while no critical bug has been found or reported in Backpack so far, we as a team need to spend more of our time on security... and you as users of our software need to update everything, from the operating system to the framework to the admin panel. The list below tells you what "safe" looks like at each layer.
8.2.35, 8.3.36 or 8.4.27, or newer. Those have the PHP2Shell fix.12.68.0 or 13.29.0, or newer.7.0.47 or newer. The latest is 7.1.26.6.8.15 or newer.5.6.2 and 4.1.72), but not the rest. Time to plan the upgrade.On May 16th, security researcher Vishal Shukla sent us a responsible disclosure report. He had found a way to run commands on a server through Backpack's telemetry code, without being logged in. It only worked on a rare combination of server settings, and we couldn't reproduce it on any of our own servers. We still treated it as the worst case. We patched v7, v6 and v5 within 24 hours, emailed customers directly, and gave everybody 30 days to update before publishing the details.
That report made us look harder. Over the next weeks, outside researchers and our own team went through CRUD line by line, and Pedro shipped fix after fix. In June we published everything that audit found:
| CVE | Severity | What it was | Fixed in |
|---|---|---|---|
| CVE-2026-54182 | High | Command injection through the Host header, no login needed | 7.0.36, 6.8.13, 5.6.2, 4.1.72 |
| CVE-2026-54180 | High | Query scopes weren't enforced on Update, Delete and Reorder | 7.0.38, 6.8.14 |
| CVE-2026-54178 | High | An admin could delete files they shouldn't, through an upload field | 7.0.35, 6.8.12 |
| CVE-2026-54175 | High | Password change on "My Account" without the current password | 7.0.34, 6.8.11 |
| CVE-2026-54177 | Medium | Upload fields kept the file extension the uploader chose | 7.0.38, 6.8.14 |
| CVE-2026-54179 | Medium | The base64 image field accepted an SVG with a script in it | 7.0.38, 6.8.14 |
| CVE-2026-54176 | Medium | Login email change on "My Account" without the current password | 7.0.38, 6.8.14 |
| CVE-2026-54181 | Medium | Stored XSS in the color column |
7.0.38, 6.8.14 |
| CVE-2026-57570 | Medium | HasMany / MorphMany fields could move a record to another parent | 7.0.47, 6.8.15 |
Most of these need a logged-in admin to exploit. That sounds reassuring until you remember what an admin panel is: the place where people you half-trust (an editor, a client, an intern) get to write to your database. A bug that lets one tenant's admin touch another tenant's records is a real bug.
We have no evidence that anybody exploited any of them. But we can't rule it out either, and that's exactly why you should update.
Then October happened, and it had nothing to do with Backpack. Three layers under every Laravel admin panel got a serious security fix within three weeks:
12.68.0 and 13.29.0.Notice what these have in common: none of them is in your code, and none of them is in ours. You can write a perfect application and still get owned through the layer underneath it.
The teams with a boring, repeatable upgrade routine patched all three in an afternoon. The teams that were three major versions behind had a very bad month.
We used to tell people to upgrade their dependencies once a year. That advice is outdated. Every 6 months is the new minimum, every 3 is better... and "the same day" is the answer when something like October drops. And it has to be the whole stack: operating system, PHP, framework, admin panel. Updating one layer and skipping the others leaves the door open.
Patching bugs is half of it. The other half is making the front door harder to open. In September we launched Multi Auth: install one package and your admin panel gets two-factor authentication, passkeys, magic link login and social login.
If your admin panel still lets people in with just an email and a password, this is the single biggest improvement you can make this year. Most break-ins don't use a clever exploit. They use a password somebody reused.
The audit didn't end in June. Pedro has kept shipping hardening releases ever since, and the latest CRUD release is 7.1.26, from November 10th. We publish the details of each fix only after people have had time to update, so the list above will get longer.
1. Check what you're running, bottom to top.
uname -r
php -v
php artisan --version
composer show backpack/crud | grep versions
2. Update the server. Install your distribution's security updates, then reboot so the new kernel is the one that's running. Update PHP the same way, and restart PHP-FPM and your queue workers afterwards.
3. Update the application.
composer update
That one command gets you the Laravel fix, the Backpack CRUD fixes, and the security updates we've pushed to Backpack PRO and our paid add-ons.
4. Got an error about access? Then your access to updates has ended, and Composer can't download the newer versions of our paid packages. CRUD is free and open-source, so its fixes are always yours. For PRO and the add-ons, you need an active plan. Which brings me to...
Until December 1st, we're running our Black Friday promo:
BF50FIRSTYEAR - 50% off your first year. For first-time customers.BF30FOREVER - 30% off every year, for as long as you renew. For everybody, including people who bought from us before.Each coupon only works for the first 50 people. And if you have a one-time license that's still active, your account has an offer to move it to auto-renew at 30% off, with nothing to pay until your current access ends.
We're moving everybody towards auto-renew for the reason this whole article exists: a project that always has access to updates is a project that gets its security fixes on day one, not sixteen months later.
--
That's the security year in review. Update everything, top to bottom. Thank you to Vishal and to everybody who reported an issue responsibly this year - and to Pedro, who fixed nearly all of them. Now go run composer update.
Cheers!
Subscribe to our "Article Digest". We'll send you a list of the new articles, every week, month or quarter - your choice.
What do you think about this?
Wondering what our community has been up to?