Most business websites are not hacked because someone targeted the business. They are hacked because an automated scanner found software that was a few versions behind. The language your site runs on (PHP for almost every WordPress, WooCommerce and Laravel site; Node.js for most modern JavaScript sites and APIs) gets security fixes every few weeks, and each fix tells attackers exactly what to look for on sites that haven't installed it.
This guide covers the part of website security that business owners can actually control: knowing what your site runs on, knowing who is responsible for patching it, and upgrading on a schedule instead of in a panic. It uses two recent cases as examples, the October 2026 PHP flaws known as PHP2Shell and the end of support for Node.js 20, because they show both kinds of risk: the sudden critical bug and the slow expiry of support.
Why website security updates can't wait
When a serious flaw is published, the gap between "fix released" and "attacks begin" is now measured in hours. PHP2Shell is a clear example. On 21 October 2026 the PHP project fixed two critical bugs, tracked as CVE-2026-109618 and CVE-2026-109619, that let someone on the internet run their own code on a web server without logging in. According to Rapid7's analysis, every PHP installation serving web requests was at risk, whether it ran through PHP-FPM, Apache mod_php, php-cgi, FrankenPHP or LiteSpeed, and the US agency CISA listed both flaws as actively exploited on 26 October. The Hacker News reported that Cloudflare saw exploit attempts climb from tens of thousands to millions within about a day of the fix.
Once an attacker can run code on your server, the damage is rarely limited to the website. They can plant malware for your visitors, copy customer data from the database, insert hidden spam pages that wreck your Google rankings, or use your server to attack others. For a business that runs ads, every hour the site shows a "this site may be hacked" warning is also paid traffic thrown away.
The stakes are highest on sites that collect personal details. Two examples from our work page show the kind: the website we built for Sadaya Healthcare takes patient enquiries, and the site for Thattil & Co is the first point of contact for a legal and advisory practice. On sites like these, an unpatched form or plugin puts other people's information at risk, not just a page of text.
Step 1: Find out what your website actually runs on
You can't patch what you don't know about. Start with an inventory, even if it is a three-row sheet:
- WordPress or WooCommerce: go to Tools → Site Health → Info → Server to see the PHP version. Plugins and themes have their own versions on the Plugins and Themes screens.
- cPanel or Plesk hosting: check "Select PHP Version" or "MultiPHP Manager". Many hosts let each site pick its own version, so check every site on the account.
- Laravel, custom PHP or Node.js apps: ask your developer to run
php -vornode -von the live server, not on their laptop, and to look at theenginesfield inpackage.json, any.nvmrcfile and theFROMline in Dockerfiles.
Then list the less obvious places: staging sites that are open to the internet, old landing pages on subdomains, cron jobs and small internal tools. The forgotten microsite on an old server is often the one that gets compromised.
Step 2: Know who is responsible for patching
Most small and mid-sized businesses in India don't run their own servers, so the real question is who applies the update.
- Shared hosting: the host patches the PHP builds, but you often choose which version your site uses. A site pinned to PHP 7.4 or 8.1 for an old plugin may not get the fix at all.
- Managed WordPress or managed cloud hosting: the host normally updates the runtime. Ask them to confirm it in writing when a critical flaw is announced.
- A VPS or cloud server (AWS, DigitalOcean, Azure, your own Linux box): you or your developer are responsible for updating packages and restarting PHP-FPM, Apache or the Node process.
The useful habit is to ask a precise question rather than accept "we keep everything updated". For PHP2Shell, the right message was: "Please confirm our server runs a PHP build that includes the fixes for CVE-2026-109618 and CVE-2026-109619, and tell us the exact version."
Step 3: Check you're on a supported, patched version
Every language publishes which versions still get security fixes. Anything outside that list is a risk even if nothing has been announced yet.
For PHP2Shell, the fixed releases were PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 or later. Sites on PHP 8.1, 8.0 or 7.4 were in a worse position: those branches no longer get routine security updates, and Rapid7 noted that the one-off backports PHP released this time can't be relied on for the next flaw. Linux distributions such as Ubuntu, Debian and Red Hat ship their own patched package versions, so the number on a managed server may differ; what matters is that the installed package includes the fix.
Node.js works on a published schedule. The Node.js release schedule shows that Node 20 reached end of life on 30 April 2026, so it gets no security patches at all. Node 22 is supported until April 2027, and Node 24 until April 2028, which makes Node 24 the sensible target for most business sites today. Newer lines become long-term support releases each October; production sites should stay on those LTS lines rather than the newest "Current" release.
End of life doesn't mean your site stops working. It means the next vulnerability found in that version stays open for good, hosting providers start retiring the runtime, and security questionnaires from payment partners or bigger clients start flagging it.
Step 4: Upgrade in staging and test the journeys that earn money
Version upgrades break things far less often than people fear, and when they do, the cause is usually an old package rather than your own code. A calm process looks like this:
- Update dependencies in a separate branch. Run
npm outdatedandnpm audit, or update WordPress plugins on a copy of the site first. Libraries with native add-ons (image processing, password hashing, database drivers) are the usual troublemakers. - Switch a staging copy to the new version. Use the same settings and database structure as production.
- Test the paths that make money. The enquiry form and the email or WhatsApp notification after it, checkout and payment callbacks, login and password reset, and your tracking (Google Analytics events, Meta Pixel and Conversions API).
- Read the logs. Deprecation warnings on the new version are a free to-do list for the next upgrade.
A five-to-ten line test script of your most valuable journeys takes ten minutes to run after every upgrade, and it pays for itself the first time it catches a broken checkout.
Step 5: Roll out with a way back
Choose a quiet window, not a sale day: for many Indian businesses that means avoiding Diwali week, Dhanteras and big marketplace sales. Before switching, back up the database and the current build, and agree in advance who can roll back and how. With containers this is easy: keep the old image tagged and ready. Watch error rates, response times and form submissions for the first 24 hours.
When you can't patch today
Sometimes the real fix has to wait, for example because a legacy plugin breaks on a newer PHP minor version. Temporary measures can reduce exposure, but they don't replace the update. For PHP2Shell, Rapid7 recommended:
- setting
session.upload_progress.enabled=0at the server level (which also blocked a third, unpatched flaw, CVE-2026-115560, in the rare setups it affected), - tightening request limits such as
post_max_sizeand blocking multipart uploads where the site never takes uploads, - applying these in php.ini or the PHP-FPM pool configuration and restarting every PHP worker, because changing them from inside the app with
ini_set()or.user.iniis too late.
Rapid7 also warned that hiding errors with display_errors does not stop an attack, and an empty error log does not prove a site is safe. If you use temporary measures, put a firm date on the actual upgrade; "temporary" has a habit of becoming permanent.
What a planned update is worth: an example
These figures are an illustrative example, not data from a real business. A WooCommerce store taking ₹1,50,000 a day in orders needs about two developer hours to patch PHP and test checkout; at ₹2,000 an hour that is ₹4,000. If the same store is compromised instead, three days offline to remove malware and restore backups costs about ₹4,50,000 in lost orders, an emergency clean-up might cost ₹40,000, and organic traffic can stay depressed for weeks while Google's hacked-site warning clears.
The same shape holds for a slower risk like an unsupported Node.js version: a planned upgrade in a quiet week costs a day or two of developer time, while a forced fix during a sale costs lost orders, urgent fees and wasted ad spend on a broken landing page.
Signs your site may already be compromised
Patching closes the door, but it doesn't remove anyone already inside. After any critical flaw, check for:
- admin users you don't recognise in WordPress or your CMS,
- unfamiliar files in upload folders, especially
.phpfiles, - redirects to other sites, particularly on mobile or from Google results,
- spam pages showing up when you search
site:yourdomain.comon Google, - a sudden security warning in Google Search Console.
If you find any of these, take the site offline or into maintenance mode, restore from a clean backup taken before the problem started, change every password and API key, and then patch before going live again.
A security update routine for the year
You don't need a security team to stay ahead of most attacks. You need a routine:
- Every month: apply CMS, plugin and theme updates on staging, test, then update the live site.
- Within days of a critical announcement: confirm with your host or developer, in writing, that the fix is installed.
- Every quarter: check that PHP or Node.js is on a supported version and note when that version's support ends.
- Always: keep an off-server backup that you have actually tried restoring.
A website is a shop front that is open 24 hours a day. Keeping its software current is ordinary maintenance, like servicing the shutter and the locks, and it costs far less than the day it fails.



