How to secure a website: why 100% secure does not exist, and what really works

No website is 100% secure, and a provider who promises you otherwise is mistaken or misleading you. Securing a site means reducing the risk and limiting the damage: here is how I go about it for my clients’ sites.

The essentials in 30 seconds

  • 11,334 new vulnerabilities were recorded in 2025 in the WordPress ecosystem, 91% of them in plugins: zero risk does not exist.
  • About half of serious vulnerabilities are exploited within 24 hours, and account takeover is the top threat for businesses in France (+45% in 2025 according to Cybermalveillance.gouv.fr).
  • On the 4 hacked sites I have repaired, the causes were always mundane: an outdated plugin, poorly managed access, a reused password, end-of-life PHP.
  • PHP 8.1 and older no longer receive any security fix, and PHP 8.2 stops on 31 December 2026: check your site’s version in the list below.
  • Maintenance costs less than a hack: from €49 excl. VAT per month for a WordPress showcase site, €199 excl. VAT for a PrestaShop store.
Read the full article

Why no website is 100% secure

A website is not a closed block: it is an assembly. On a WordPress site or a PrestaShop store, you find the CMS itself, about twenty plugins or modules written by different publishers, a theme, PHP, a database and the server. Each of these building blocks can contain a flaw that nobody knows about yet.

The figures show it. According to Patchstack’s annual report, 11,334 new vulnerabilities were recorded in the WordPress ecosystem in 2025, 42% more than in 2024. 91% concern plugins, 9% themes, and only 6 the WordPress core. In other words, the risk comes mostly from what you add to the site.

Another figure that matters: about half of serious vulnerabilities are exploited within 24 hours of being published. Attacks are automated: bots constantly test thousands of sites, with no idea who you are. A small business is not “too small to interest hackers”: it is simply on the list, like everyone else.

What I found on the hacked sites I repaired

I have put 4 hacked sites back in order. None of them had suffered a sophisticated attack: each time, the attacker came in through a door left open.

  • An outdated plugin or module: the flaw was known, the fix existed, it simply had not been installed.
  • Poorly managed access: the account of a former provider that was never deleted, FTP access left open, a password that was too simple.
  • A reused password: the same password was used on several sites. One site was hacked first, and the attacker used the stolen password to get into the others. It is the most common human error, and the easiest to avoid with a password manager.
  • End-of-life PHP or hosting: no more security fixes are published, so the flaws stay open for good.

This matches the national figures in France: in 2025, account takeover was the top threat for businesses, up 45%, according to the activity report of Cybermalveillance.gouv.fr (in French). Website security is mostly about regularity and simple habits, not a miracle tool.

Is your site running on a version that is still maintained?

A version that no longer receives security fixes is the most lasting way in: the flaw is public, and nobody will fix it. Here is where the most common building blocks stand as of 6 November 2026.

PHP

  • PHP 7.4: no more fixes since 28 November 2022.
  • PHP 8.0: no more fixes since 26 November 2023.
  • PHP 8.1: no more fixes since 31 December 2025.
  • PHP 8.2: security fixes until 31 December 2026.
  • PHP 8.3: security fixes until 31 December 2027.
  • PHP 8.4: maintained until 31 December 2028.
  • PHP 8.5: maintained until 31 December 2029.

PrestaShop

  • PrestaShop 1.6: unmaintained for years.
  • PrestaShop 1.7: fixes stopped with the release of PrestaShop 9 (June 2025); the last one, 1.7.8.11, dates from January 2024.
  • PrestaShop 8.2: security fixes only, until PrestaShop 10 is released.
  • PrestaShop 9: maintained.

On the module side, the Friends of Presta collective has published more than 220 security advisories about PrestaShop modules since 2022, 141 of them in 2023 alone: as with WordPress, the risk mostly comes from the modules you add, not from the core.

WordPress

  • Latest version: the only one officially supported.
  • Versions 4.7 to the previous major: fixes backported "as a courtesy", with no guarantee.
  • Versions 4.6 and older: no more fixes since July 2025.

I update this list whenever support ends. To find out where your site stands, the express audit checks it in detail.

What really reduces the risk

Update fast, but on a copy first

Updating is the most effective protection, since most hacks exploit flaws that have already been fixed. But an update can also break a theme, a payment module or a form. So I test every important update on a copy of the site before applying it live. That is what lets you move fast without risk.

Tested backups, stored off the server

A backup that has never been restored is not a backup, it is a hope. It must be daily, contain the files and the database, be stored somewhere other than the site’s server (otherwise the hacker encrypts or erases it along with the rest), and be restored for real from time to time.

Fewer plugins, fewer access points

Each plugin is one more door. I remove those that are no longer used, and I prefer one well-maintained plugin to three abandoned ones. The same logic applies to access: one account per person, unique passwords, two-factor authentication on the admin area, and accounts of former providers deleted.

Monitor to react quickly

Since zero risk does not exist, you need to know quickly when something happens: site offline, modified files, suspicious pages indexed by Google, error spikes. A hack discovered within hours is repaired in a day; discovered three months later, it has often damaged search ranking and reputation.

HTTPS is not enough

The browser padlock encrypts exchanges between the visitor and the site. It is essential, but it says nothing about the security of the site itself: an HTTPS site can very well be hacked.

And if the site is hacked anyway?

This is where all the upstream work pays off. With clean backups and monitoring, a hack becomes an incident, not a disaster. My method: get the site back online in under 2 hours with a temporary fix, then clean it in depth and close the way in. That is what I did for Parismatic Tour, a tour agency in Paris, before building a custom booking site (see the Parismatic Tour case study).

If your site is hacked today, the first reflexes are simple: do not delete everything in a rush, change passwords from a clean computer, notify your host, and have the site cleaned while looking for the flaw, otherwise the hacker comes back. I detail the steps on the hacked website repair page.

How much does website security cost?

Much less than a hack. With me, maintenance of a WordPress showcase site starts at €49 excl. VAT per month: updates, backups and monitoring. For a PrestaShop store, the Store plan at €199 excl. VAT per month includes updates tested on a copy and 2 hours of work. The plans are detailed on the website maintenance plans page.

Not sure where your site stands? An express audit at €290 excl. VAT takes stock of versions, plugins, access and backups, with a prioritised and costed list of fixes: see the website audit service.

Sources

How to secure a website: frequently asked questions

Can a website be 100% secure?

No. New vulnerabilities are discovered every week in CMSs, plugins and servers. You can greatly reduce the risk and limit the damage, but not remove it.

My site is small, are hackers really interested in it?

Yes. Attacks are automated: bots test thousands of sites looking for known flaws, whatever the size of the business.

Is WordPress less safe than other CMSs?

The WordPress core is rarely affected: 6 vulnerabilities in 2025, all of low severity. The risk comes mostly from plugins and themes, and from sites that are not updated.

Is HTTPS enough to secure a website?

No. HTTPS protects exchanges between the visitor and the site, not the site itself against a vulnerability or a stolen password.

How quickly should security fixes be applied?

Security fixes as soon as they are released, ideally within 24 to 48 hours, since serious flaws are often exploited the same day. Major updates, after a test on a copy of the site.

How much does website security maintenance cost?

At DataPet, from €49 excl. VAT per month for a WordPress showcase site and €199 excl. VAT per month for a PrestaShop store.

How do I know if my site’s version is still maintained?

Check the PHP version in your host’s customer area and the CMS version in your site’s admin, then compare them with the list in this article. PHP 8.1 and older, and PrestaShop 1.7 and older, no longer receive security fixes.

Read next

Let’s talk about your project

Write to me: I reply within one working day, with a first opinion or an offer of a 30-minute video call, even if we never work together.