This sheet is past its review date. Deadlines or advice may have changed since 5 Nov 2026.
Websites and CMS: who patches your site, and how fast?
This week, get every site's PHP patched for October's exploited flaws. This month, turn on automatic updates for core, plugins and themes, require MFA for every admin, plan the move off PHP 8.2 and Drupal 10, which lose support in December, and write down who patches and who restores the site when it is hacked.
If you only do five things
Write down who patches what.
In agency and hosting contracts, name who updates the CMS, plugins and PHP, who restores, and how fast. German law makes businesses secure web systems against unauthorized access, within reason and considering the state of the art7.
If the site is hacked
Take it offline and keep the evidence.
Show a maintenance page, then copy the files, database and all logs, or have the hoster do it, before anything changes10.
Lock everyone out.
Change the passwords for CMS users, SFTP, the hosting panel and the database. In WordPress, replace the secret keys in
wp-config.phpto end all sessions11.Find the way in.
Check for new admin accounts, recent plugins, changed PHP files and
.htaccess11. Unless you fix the entry point, the site gets hacked again10.Rebuild from clean sources.
Restore a backup from before the attack, or reinstall core and plugins from official copies1011. Update everything, then change the passwords again11.
Tell the people who need to know.
If customer or card data may be affected, follow the incident response sheet and call your payment provider. Once clean, request a review in Google Search Console12.
Updates, plugins and PHP
- Check WordPress's settings. Minor releases update automatically, but major ones only on sites installed since 5.613. Enable both under Dashboard > Updates.
- Buy premium plugins in the company's name. WordPress shows updates for plugins installed from a ZIP file only if the vendor built in an updater15. Never use nulled copies from untrusted sources3.
- Replace abandoned plugins. Check each plugin's last release once a quarter, and replace any that no longer get updates.
- Patch PHP separately. CMS updates don't fix the PHP runtime, and containers need a rebuild18. Set a PHP patch deadline with the hoster.
Admin access, agencies and hosters
- One account per person. No shared agency logins. Keep admin rights to a few named people and give content staff an editor role.
- Prefer company SSO. Sign admins in through your identity provider with SAML or OpenID Connect, so leavers lose access with their account.
- Restrict the admin path. Allow the backend only from VPN or office IPs, with TYPO3's
IPmaskList4 or web server rules, and limit failed logins19. - Own every account. Keep the domain, hosting, CDN, repositories and licenses in the company's name; registrar locks are in the DNS and domains sheet. When an agency leaves, remove its accounts and rotate SFTP, database and API credentials.
Online shops: scripts on the payment page
- Know your setup. PCI DSS 6.4.3 and 11.6.1 cover scripts on payment pages and on pages embedding the provider's iframe; with a redirect, confirm the scope with your acquirer or QSA23. SAQ A drops both, but iframe users must confirm their site resists script attacks24.
- Authorize every script (6.4.3). Confirm each payment page script is authorized, assure its integrity and list it with a reason23.
- Detect changes (11.6.1). Alert on unauthorized script and security header changes as browsers see them, weekly or per risk analysis23.
- Cut scripts from checkout. Keep tag managers, chat widgets and pixels off payment pages, and limit sources with a Content Security Policy23.
Hosting, backups, WAF and forms
- Back up outside the hosting account. Keep dated snapshots from before any compromise3. Restore tests are in the backups sheet.
- Treat a WAF as time, not a fix. For PHP's October flaws, the BSI said only patching or going offline protects fully18. Wordfence's free plan gets new firewall rules 30 days late5.
- Lock the origin behind your CDN. Accept only CDN traffic, through an IP allowlist, authenticated origin pulls or a tunnel25.
- Restrict uploads and forms. Fix allowed file types, sizes and folders, with no execute rights, and block bots without locking out real users19.
End-of-support dates that set your schedule
- PHP. 8.1 and older get no releases; for October's flaws, the PHP project offered only source backports20. 8.2 ends on 31 Dec 2026, 8.3 on 31 Dec 20278.
- Drupal. Drupal 7 ended on 5 Jan 2025. Drupal 10 ends on 9 Dec 2026, the week 12.0 ships9.
- TYPO3. Only v14 and v13 get free fixes16. v12 lost them on 30 Apr 2026; paid ELTS runs to 30 Apr 2029, or 2030 via a TYPO3 partner21.
- Joomla. 5.x gets security fixes until 12 Oct 2027, 6.x until 16 Oct 202922.
- WordPress. Only the newest version is actively supported14.
- Shopware. Its security plugin covers only versions still in support17.
What changed in 2026
- PHP needed an emergency patch. On 21 Oct 2026, PHP fixed two critical unauthenticated code execution flaws20. CISA listed both as exploited on 26 Oct26. Check each site's PHP against its Linux distribution's patched package18.
- WordPress core entered CISA's KEV catalog. Four core flaws were added from July to November 202626.
- Hosting panels were exploited. CISA lists a cPanel login bypass used in ransomware attacks, and a LiteSpeed cPanel plugin flaw that gave any cPanel user root26.
- Other platforms too. CISA added a Drupal core flaw in May, flaws in five Joomla extensions in June and July, and three Adobe Commerce flaws since September26.
What you can skip
- Renaming the admin URL. It doesn't stop an exploit. Restrict the path instead, and spend the time on updates and MFA.
- A second or third security plugin. Each one is more code to patch. One security plugin is enough.
- Staging every security release. WordPress strongly discourages turning off minor auto-updates13. Stage major upgrades only.
- Perfect scores on header and TLS scanners. Apply the encryption sheet's TLS baseline and a CSP on checkout, then get back to updates.
Mistakes that cost the most
- Restoring a backup and calling it fixed. Backdoors survive, such as a harmless-looking admin account or hidden PHP file10.
- Deleting only the obvious malware. Attackers often inject code into existing files10. Replace core directories with clean copies11.
- Assuming someone else patches. Check that the contract covers plugins, PHP and a fast response to a compromise6.
- Forgetting old sites and APIs. Microsites, staging copies and shop APIs need care too. See the attack surface and API security sheets.
What this looks like at your size
Small team, no security staff
- Ask your agency or hoster in writing who updates core, plugins and PHP, and to fix exploited flaws within 72 hours.
- Turn on automatic updates and admin MFA.
- Take card payments on your provider's hosted payment page, not in your own form.
Growing, with IT or security staff
- List every site and staging copy with its owner, CMS, PHP version and end-of-support date.
- Sign admins in through your identity provider and allow the backend only from VPN or office IPs.
- Put a WAF or CDN in front, lock the origin to it and check files for unexpected changes6.