We already compared WordPress and Next.js on speed. This is the other, less pleasant topic: security, with sourced numbers.

The problem rarely comes from WordPress itself
WordPress runs a very large share of the world's websites. Its core software is closely watched and regularly fixed by its team. Most security flaws come from somewhere else: the plugins people install on top of it.
Patchstack, a company that tracks WordPress security flaws, publishes a report every year. In 2024, 96% of the flaws it found were in plugins, 4% in themes, and only 7 flaws in WordPress core. In 2025, plugins still made up 91% of the flaws.
So a well-kept WordPress site, with a few plugins that are all up to date, doesn't carry the same risk as a site with fifteen plugins added over the years, some of them forgotten.
Why plugins are the weak spot
There are tens of thousands of WordPress plugins, made by very different teams. Some are serious and looked after. Others were abandoned years ago.
According to the same Patchstack report, 43% of the flaws found in 2024 could be used without having an account on the site. That makes them easy to exploit in bulk: a bot tries them on thousands of sites at once. Nobody has to be after your site in particular for it to get hit.
The risk also grows with time. The older a site gets, the more plugins it collects, and the harder it becomes to know which ones are still needed and which ones are up to date.
What a hack really costs
With specialist services, just cleaning up a hacked site costs anywhere from a few hundred to a few thousand dollars, depending on how bad it is. And that is only part of the bill.
Add the days when the site is offline and no customer can find you, the Google visits you lose if the site gets flagged as dangerous, and the time spent putting everything back in order. Then there is the trust you lose when a customer opens your site and lands on a suspicious redirect or an error message.

What a hacked site looks like to your customers
Many people picture a hack as a black screen with a threatening message. In real life, it's rarely that obvious. The hacker isn't trying to scare you. They want to use your site for as long as possible, without you noticing.
Often the site looks normal when you open it yourself, logged into your account. The problem only shows up for some visitors: people coming from Google, people opening the site on a phone, or people visiting from another country. So you can have a hacked site for weeks without seeing anything.
Here is what your customers might run into instead of you:
- A redirect to a gambling site, fake giveaways or scams, a few seconds after your page opens.
- Pages in a foreign language, with product names you don't sell, showing up in Google under your site's name.
- Windows that pop up on their own and ask to install an app or to 'update' the phone.
- A contact form that no longer sends you anything, even though the site seems to work.
- Emails sent in your name that you never wrote.
Google warnings and blacklists
Google keeps an eye on dangerous sites to protect people online. When it spots a site that has been hacked or is being used to trick people, it can show a warning. In search results, the note 'This site may be hacked' can appear under your name. And in the Chrome browser, visitors may land on a big red page telling them not to go any further.
Few customers get past that red page. Most close it and look elsewhere. And the ones who already know you start wondering what's going on with your business.
Google explains these issues in its Search Console security issues report. Once the site is clean, you have to ask Google to review it again. Until that's done, the warning can stay. That's one more reason to connect your site to Search Console: it's often where you hear about the problem first.
There are also blacklists for email. If a hacker uses your site or your server to send spam, your domain name can end up on one. The result: your real emails, your quotes and your invoices, land in your customers' spam folder. Getting off these lists takes time, and the problem has to be fixed at the source first.
What a hack costs a business in Algeria
The repair bill is only part of the cost. In Algeria, many customers reach your site from Facebook, Instagram or a link shared on WhatsApp. They open it on their phone, often on 4G, in between other things. If they hit a strange page or a red warning, they won't try to figure it out. They'll message your competitor.
For a store that lives on cash-on-delivery orders, every day the site is down means orders that don't come in. And if the hack lands during Ramadan, right before Eid or in wedding season, the loss is heavier, because that's when customers search the most.
Then there's your reputation. In a town or a wilaya where everyone knows each other, a line like 'their site sent me to a scam' travels fast. A customer who got scared once is slower to come back, even after everything is fixed. We talk about this trust question in our article on what makes a website feel trustworthy to Algerian customers.
Finally, many services that specialize in cleaning hacked sites are abroad and charge in foreign currency. For an Algerian business, that isn't always simple, or quick.
No need to panic: just know what's running on your site
WordPress is still a good tool. Plenty of WordPress sites run for years without ever being hacked. The question to ask is simple: does anyone know what's installed on the site, and is someone really keeping it up to date?
A site left alone for years, with plugins nobody maintains anymore, is at real risk. A site that someone checks regularly is at much less.
Signs a WordPress site is at risk
If you already have a WordPress site, some signs should get your attention. None of them means the site is hacked, but each one opens another door:
- Nobody can say how many plugins are installed anymore, or what each one does.
- Updates have been waiting for months, because nobody dares run them in case something breaks.
- Plugins or themes that are no longer used are still there, just switched off.
- The same admin password has been used for years, sometimes shared between several people or past developers.
- The site has started slowing down, showing strange pages or sending visitors to other sites, for no known reason.
Cheap hosting: a risk you don't see
Many WordPress sites in Algeria run on very cheap shared hosting. The idea: hundreds of sites on the same server, sharing the same resources. That isn't always a problem. Some shared hosting companies are serious and well run.
But when the price is very low, it's worth asking where the savings come from. Often it's from monitoring, server updates and support. A server that is overloaded, poorly kept and running old software leaves more doors open. And if a neighboring site gets hacked, the problem can sometimes spread to other sites on the same server.
There are also simple questions few people ask before buying. Who answers if the site goes down on a Friday evening? Are backups made, and where are they kept? Does the host warn you when it spots a problem, or does the customer find out first? Cheap hosting that can't answer any of these often turns out expensive the day something goes wrong.
Outdated plugin or abandoned plugin: the difference matters
An outdated plugin is one whose author has fixed a flaw, but the fix hasn't been installed on your site yet. The risk is real, but a solution exists.
An abandoned plugin is worse. Its author no longer looks after it. If a flaw is found tomorrow, no fix will ever come. The plugin stays installed, it keeps working, and nobody sees the danger. It's often this kind of plugin, added years ago for one small feature, that opens the door.
Another case comes up often here: paid themes and plugins downloaded from unofficial sites in 'cracked' versions. It's tempting, especially when paying in foreign currency is hard. But these files are sometimes changed to hide a way in. The site works, the theme looks great, and the hacker already has a key. On top of that, these versions never get security updates.
So the real cost of a theme or plugin isn't just its price. It's also the question of who will still be looking after it in two or three years.
Who is responsible for your site's security?
Almost nobody asks this question, and it's often where everything is decided. Around a website there are usually several players: the person or agency that built it, the hosting company, sometimes a maintenance provider, and you, the owner.
The problem is that each one thinks it's someone else's job. The person who built the site delivered it, got paid and moved on. The host says it looks after the server, not what's on it. And the owner thinks 'the developer handles it'. In the end, nobody runs the updates.
A few points are worth making clear, in writing:
- Who runs the updates, and how often?
- Who has admin access, and is that access removed when a provider leaves?
- Are the domain name and hosting in your name, or in the name of a past provider?
- Who warns you, and who steps in, if the site gets hacked?
Backups: the question to ask before it's too late
When a site is hacked, a good backup changes everything. It lets you go back to a clean version instead of rebuilding from scratch. Yet many owners find out on the day of the problem that there isn't one, or that it's useless.
Having 'backups' isn't enough. What matters is knowing where they're kept, how recent the latest one is, and whether anyone has ever checked that the site can really be put back online from them. A backup kept on the same server as the site can disappear with it. And a backup made after the hacker got in already contains the problem.
If you can't answer these questions for your site, that's okay. But now is the right time to ask whoever looks after it, before you need it.
How we choose the technology for a new site
As we said in our WordPress vs Next.js comparison, WordPress is still a good choice for some projects, especially if you want to edit your content yourself, and we still audit and maintain WordPress sites. For the new sites we build, we choose Next.js. Speed comes first, then security: with fewer third-party plugins to watch, there are fewer doors to keep shut.
In the end it's a practical question: how much time will someone have to spend each month watching what runs on your site to keep it safe?
No site is hack-proof, not even with Next.js
Let's be honest: choosing Next.js doesn't make a site impossible to hack. A Next.js site has fewer third-party plugins, so fewer doors. But there is still hosting to watch, passwords to protect, forms to secure and a domain name account to keep locked down.
In the same way, a WordPress site isn't doomed. With few plugins, all looked after, good hosting and someone who really takes care of it, it can stay safe for years. It also lets you edit your own pages, which matters to many businesses.
So security doesn't depend only on the tool. It depends mostly on follow-up: does someone know what runs on the site, and check it regularly? That's the first question we ask when we take over any site, whatever it's built with.
How SimplerWebs can help
- Website maintenance: we keep your site up to date and watch for signs of trouble before they turn into a hack.
- Website redesign: if your WordPress site has aged and collected forgotten plugins, we look with you at what is worth keeping.
- Custom website: for a new project, we start from a clean base that won't need hours of watching.
In short
WordPress security flaws mostly come from plugins, and the risk grows if nobody keeps an eye on what runs on the site. Fixing a hacked site often costs more, in money and time, than looking after it regularly.
Not sure where your current site stands? We can look at it with you.
Read next
Frequently asked questions
Is WordPress dangerous by itself?
No. The core software is well looked after. Most flaws come from the plugins installed on it: 96% of the WordPress flaws Patchstack recorded in 2024.
How many plugins is too many?
There is no set number. The real problem isn't the count, it's when nobody knows what each plugin does or whether its author still looks after it. A forgotten plugin is often the one trouble comes through. We can go through them with you.
Do I need to drop WordPress to be safe?
Not necessarily. A well-kept WordPress site with a few up-to-date plugins is a reasonable choice. We recommend Next.js for most of our new projects, but WordPress is still a valid option.
How do I know if my WordPress site is at risk?
Start by checking how many plugins are installed, whether they're up to date, and whether you still know what each one is for. Our SEO audit also reviews the technical state of your site.
What do I do if my site is already hacked?
Act fast. The longer a site stays infected, the more the repair costs and the more trust your customers lose. We can point you in the right direction, even if we didn't build the site.
Can my site be hacked without me noticing?
Yes, and it happens often. Many hacks only show up for visitors coming from Google or on a phone, not for the owner logged into their account. A customer telling you about a strange page, or odd results under your name in Google, is often the first sign.
Does my hosting company take care of my site's security?
Usually the host looks after the server, not what runs on it. Updates to WordPress, the theme and the plugins often stay your job or your provider's. The best move is to ask in writing what your plan includes.
Does a Google warning go away on its own?
Not always. The site first has to be fully cleaned, then you ask Google to review it again from Search Console. As long as the problem is still there, the warning can stay up.
