Security & Plugin Updates
Regular updates for your CMS, plugins, modules and dependencies, tested before they go live, so known holes are closed and nothing breaks.
Based in Hamburg, Germany, working remotely with clients across Germany and abroad, in German or English.
Request an AI summary
Most attacks on websites don’t target a specific business. Automated scanners look for known vulnerabilities in outdated software and try them on millions of sites. Keeping everything up to date is the most effective protection against that, as long as updates don’t break the site along the way.
Scope: what gets updated
- CMS core: WordPress, Shopware and other systems, including major versions.
- Plugins, extensions and modules: the most common entry point for attacks.
- Dependencies: frameworks and packages in custom code.
- Server and runtime: PHP, Node.js and database versions checked; they’re updated in your hosting account, and I help where needed.
- Certificates and headers: HTTPS, TLS settings and security headers.
Process: tested, then live
Updates are checked against their changelogs, applied to a staging copy first and tested on the pages that matter most, such as forms, checkout and sign-in. Only then do they go live, with a fresh backup in place and a way back. Critical security fixes are applied as soon as they are released, routine updates on a fixed schedule.
Housekeeping: fewer plugins, less risk
Every plugin is a possible weak point and a little extra loading time. Only plugins in active use stay installed; two that do the same job become one, and sometimes a small piece of custom code is more reliable. Plugins that stop getting updates from their developers are flagged early, with a replacement planned before a new vulnerability forces a rushed change.
Result: what you get
A site on current, supported software, a log of every update and one contact person when something needs a decision.