| Security

How small business websites actually get hacked

Almost nobody chooses your website. Software scans the entire internet looking for one known weakness, finds every site that has it, and walks in. Understanding that one fact changes which precautions are worth taking - and it rules out most of the ones people worry about.

There is a picture most people carry of what a website hack looks like: somebody who has decided to come after your business, working at it. For a bank or a government that is sometimes true. For a dental practice, a construction firm or a clothing shop, it almost never is - and believing it leads people to spend money in the wrong places.

Nobody picked you

What actually happens is industrial. A flaw is found in a piece of software that millions of websites run - a plugin, a theme, a version of PHP, a shop extension. It is published, because publishing it is how everybody gets the fix. Within hours, automated software begins working through the internet address by address, testing every site it finds for that one weakness. It does not know what your business is or care. Your site either has the flaw or it does not.

That is why "we are too small to be a target" is the one belief worth dropping entirely. Being small is not protection, because nothing is aiming. It is also oddly reassuring: a problem caused by a machine running down a list can be solved by not being on the list, and that is an ordinary maintenance job rather than a security one.

The four stages of an automated website attack: a flaw is published, scanners sweep the internet, vulnerable sites are found, and access is used or sold
Nothing in this sequence involves a decision about your business. The gap between stage one and stage three is usually hours.

What the figures actually say

Search this subject and you will be given confident, contradictory numbers. In the same week we found "phishing is the top attack on small businesses at 33.8%", "stolen credentials are the leading way in at 22%" and "vulnerability exploitation leads at 26%", each stated as established fact. They cannot all be the leading one.

They disagree because they count different things - all breaches against one industry’s subset, insurance claims against investigated incidents, different years - and because many of them are quoting each other. So rather than add to the pile, here is the single most widely used primary source, with its own caveats included.

Verizon’s 2026 Data Breach Investigations Report found that where the initial way in was known, exploiting a known software flaw accounted for 31% of breaches, up from 20% the year before - overtaking credential abuse, which fell to 13%. Verizon notes in the same report that the comparison is not clean: measured the way they measured it last year, credential abuse would have come in at 16%, and counted anywhere in the attack rather than only as the first step, it appears in 39% of breaches. The median time organisations took to patch a flaw was 43 days, up from 32.

A figure we are deliberately not quoting. The report does break initial access down by organisation size, and it would be useful to give you the small-business number. The published breakdown is not labelled clearly enough to attribute one to small businesses with confidence - the range across those tables runs from 26% to 47% - so quoting a specific one would be inventing precision. The overall figures above are solid; the SMB split is not, and anybody giving you one to the decimal place has not checked.

The practical reading of all this is narrower than it looks. Whichever source you prefer, two things sit at the top of every list: software nobody updated, and credentials that should not have worked. Both are maintenance. Neither needs a security product.

The ways in, in rough order

Ordered by how often we actually find them, which broadly matches the published data for the top two:

01

An out-of-date plugin, theme or extension

The commonest by a distance on WordPress and WooCommerce sites. The flaw is public, the fix is published, and the site sat on the old version for months. Abandoned plugins are worse: there is no fix coming at all.

02

The platform or language underneath

PHP, the CMS core, the database. Less frequent than plugins but far more serious when it happens, because it is below everything you can see. This is what we wrote about in the PHP article below.

03

A password that was guessed or reused

Either guessed outright by software working through common passwords against your login page, or taken from an unrelated breach somewhere else and tried here because the same one was used twice.

04

Access that was never removed

An old developer’s SSH key, an FTP account made for a one-off job, a staff login that outlived the staff member. Nothing has to be broken for this to work - the door is legitimately open.

05

A form or upload that accepts too much

Contact forms, file uploads, search boxes and URL parameters that pass whatever they are given straight to the database or the file system. Mostly a problem on custom-built sites rather than mainstream platforms.

06

The owner’s own email or computer

If the attacker can read your email they can reset every password you own. A hacked website is sometimes the second thing that happened, not the first.

What they do once they are in

Rarely anything dramatic, and that is the point. A defaced homepage tells you immediately; the profitable versions are quiet:

  • Spam pages hidden in your site. Hundreds of pages about products you do not sell, invisible to you but indexed by Google, borrowing your domain’s reputation. Usually discovered when Google flags the site, by which point the rankings are already gone.
  • Redirects that only fire for strangers. Visitors from Google get sent elsewhere; anybody typing the address directly, or logged in as you, sees the normal site. This is why owners are often the last to know.
  • Card skimming on checkout. A few lines added to the payment page that copy the card details as they are typed. The order completes normally. Nothing looks wrong at either end.
  • Your server used for something else. Sending spam, hosting files for another scam, or joining in attacks on other people. The first sign is usually your host suspending the account or your email landing in everyone’s spam folder.
  • Nothing at all, for now. A quiet backdoor left in place and sold on. Access is a product.

How long you can stay broken into without knowing

Months, routinely. None of the quiet versions above interfere with the site working, and the ones that hide from logged-in users are specifically built so that the owner sees nothing. The usual way people find out is from outside: Google marks the site, the host suspends it, a customer reports a strange redirect, or the card company calls.

That is the real argument for checking something monthly rather than buying anything. You are not trying to be impenetrable. You are trying to not be the site that has been quietly open since March.

The fixes that do most of the work

Ranked honestly by how much risk each removes for the effort, not by what is easiest to sell:

Update things, on a schedule

Plugins, themes, the CMS and the PHP version, monthly and on a date. This alone addresses the largest single category in every dataset. Remove what you no longer use rather than updating it.

Unique passwords and two-factor

Different password everywhere, and two-factor on the CMS admin, the hosting account and the email behind them. Reuse is what turns somebody else’s breach into yours.

Shorten the access list

Remove old developers, dead FTP accounts and staff who have left. An hour, once, and it closes doors that no update will.

Backups you have restored from

Off the server, kept long enough to pre-date a quiet infection, and tested at least once. A backup nobody has ever restored is a hope.

That is the whole list. Four things, none of them technical, and together they cover the overwhelming majority of how small business sites are actually broken into. If you would rather it was somebody’s job than yours, that is what a care plan is: the updates get done on a date, and you hear about it afterwards.

What is not worth your money

Said plainly, because this is where small businesses are sold things:

  • A security plugin instead of updates. It will show you a dashboard and a score. It does not fix the out-of-date plugin that is the actual hole. Useful alongside maintenance; useless in place of it.
  • Hiding your login page. Marginally raises the effort for automated guessing and does nothing against a flaw in your software. Two-factor is the version of this that works.
  • "Hack-proof" anything. Nobody can offer that, and offering it is the clearest sign to buy elsewhere. What can be offered is prompt updates, a short access list and a tested backup.
  • An SSL certificate as security. HTTPS protects data moving between the visitor and your site. It does nothing about who can log in. Have it - it is free and Google expects it - but it is not this.

Where to start today

Three things, in this order, none of them long. Open your CMS and look at how many updates are waiting and how old the oldest one is. Open your hosting panel and check who can still log in. Then find out when your last backup was taken and whether anybody has ever restored one.

If all three are fine, you are in better shape than most. If one of them makes you uncomfortable, that is the one to fix this week - and the free website audit will tell you in twelve seconds what your site is announcing to the outside world while you decide.

| Questions

Questions people ask about this

Why would anyone hack a small business website?

Usually nobody chose to. Automated software scans the whole internet for one known weakness and takes every site that has it, without knowing or caring what the business is. The value is not your data specifically - it is a working server that can host spam pages, redirect your Google traffic, skim card details or simply be sold on as access.

What is the most common way websites get hacked?

Out-of-date software, consistently. Verizon’s 2026 Data Breach Investigations Report found that exploiting a known flaw accounted for 31% of breaches where the initial access was known, up from 20% the year before and ahead of credential abuse at 13%. On small business websites specifically, that most often means an un-updated plugin, theme or extension.

How would I know if my website has been hacked?

Often you would not, for months. The profitable versions are quiet: hidden spam pages Google can see but you cannot, redirects that only fire for visitors arriving from search, or a few lines on the checkout copying card details. Most owners find out from outside - a Google warning, the host suspending the account, or a customer reporting something strange.

Does a security plugin keep my website safe?

Not on its own. A security plugin can block some automated noise and tell you when files change, which is worth having. It does not close the out-of-date plugin that is the actual way in. Treat it as something that sits alongside regular updates, never as a replacement for them.

Is my website safer if it is small or new?

No, because nothing is aiming at it. Attacks are run by software working through lists of addresses, so the size of your business does not enter into it. A one-page site on current software is far safer than a large one running a plugin last updated in 2023.

Does an SSL certificate protect my site from hackers?

It protects information while it travels between your visitor and your server, which matters and which Google expects. It does nothing about who can log in to your site, and nothing about a flaw in your software. HTTPS is necessary and it is not security on its own.

How often should a business website be updated for security?

Monthly is the right rhythm for most sites, plus promptly whenever a serious flaw is published in something you run. The published median time to patch is 43 days, which is roughly how long an automated scanner has to find you first.

Want to know what your site is leaving open?

The free audit checks what the outside world can see in twelve seconds. Or send us the address and we will look properly.

WhatsApp us