

Your website works. Customers can visit it, browse your services, fill in forms or buy your products. Everything seems to be in order.
But do you know which version of PHP it runs on? When was its security last reviewed? Who is responsible for checking that the components it was built with are still up to date?
It's quite common for a business to know exactly what's happening on its website from a commercial point of view, but to be much less clear about the technology behind it.
And these questions usually don't come up until a problem appears.
The recent PHP security alert is a good example of why it pays to keep an eye on what you can't see as well.
On 21 October 2026, updates were released to fix two critical PHP vulnerabilities, identified as CVE-2026-109618 and CVE-2026-109619.
PHP is a programming language used by a huge number of websites, including those built with WordPress, WooCommerce or PrestaShop.
Without getting too technical, under certain conditions these flaws could allow an attacker to run code on a server without authorised access.
Does this mean every website that uses PHP is at risk? No.
The risk depends on the installed version, the server configuration and whether the relevant fixes have been applied.
But it is a serious enough alert to warrant a check, especially if nobody has looked at the technical side of your website for a while.
At La Teva Web we work on digital projects for very different businesses, and there's one situation we know well: websites built years ago that still work, but whose technology hasn't been properly reviewed in a long time.
And that's understandable. If the site loads correctly, the forms work and customers can buy, why would you think there's a problem?
Because what we see when we browse a page is one thing, and what happens behind it is another.
Over time, plugins stop being supported, new versions of PHP come out and some older developments start to show incompatibilities.
Then a major update arrives and we find that it can't be applied without first reviewing other components.
What should be a fairly simple task ends up becoming a much more complex job.
That's why maintaining a website isn't just about updating WordPress every now and then. It also means reviewing the server, PHP versions, extensions and the features the business needs.
The first check is to find out which version of PHP the server hosting your website uses and confirm whether the relevant patches have been applied.
The official versions that include the fixes are:
PHP branch | Patched version |
PHP 8.5 | 8.5.12 |
PHP 8.4 | 8.4.27 |
PHP 8.3 | 8.3.36 |
PHP 8.2 | 8.2.35 |
Some hosting providers use packages with their own security patches, so a different version number doesn't necessarily mean the installation is vulnerable. In these cases, you need to confirm with the provider which fixes have been applied.
If your website uses an old version of PHP, especially one that no longer receives official support, it's worth looking at how to upgrade it.
But be careful: we don't recommend changing the PHP version directly on a live website without checking compatibility first.
An update can fix a security issue and cause others if the site uses plugins or developments that aren't compatible with the new version.
In an online store, for example, it could affect the checkout process, payment gateways or order management.
Before updating, it's important to have a backup, review the affected components and then check that everything still works properly.
You don't need to. That's what the professionals who maintain it are for.
At La Teva Web we can review the technical state of your website, check whether it needs any updates and help you decide how to carry them out safely.
Ask our team about the state of your website
This is where a one-off alert can help uncover problems that have been building up for some time.
When reviewing PHP, you may find plugins that no longer receive updates, features that depend on outdated technologies or developments that have been modified over the years without anyone reviewing their structure.
Not all of these situations mean you need a new website.
Many websites can keep working perfectly well with proper maintenance and a few technical improvements.
But there are also cases where continuing to update and patch old components becomes more complicated than is reasonable.
And that's when another question comes up: is it worth continuing to invest in the current website, or is it time to redesign it?
The answer depends on many factors: how it's built, which components it uses, what problems it has and, above all, what the business needs today.
Because a website redesign shouldn't be considered purely for aesthetic reasons. It can also be an opportunity to improve performance, simplify maintenance, update the technology and develop features that weren't possible before.
Beyond this specific vulnerability, there are a few situations that should get your attention.
None of these signs automatically means you need a new website. But they are good enough reasons to look into what's going on.
If you have a maintenance service in place, the first step is to ask your provider whether your installation is affected and whether the necessary fixes have already been applied.
These are the questions worth asking them:
If you don't have a maintenance provider, don't know who handles the technical side or nobody has reviewed your website for a while, the best thing to do is request a professional assessment.
Not necessarily to change it. First, to find out what state it's in.
When a business comes to us with a problem on its website, the solution isn't always the same.
Sometimes it's enough to update PHP, review a few components and set up proper maintenance.
Other times we find outdated technologies that make updates difficult, limit new features or mean that any change takes more work than it should.
In those cases, it makes sense to consider whether to modernise part of the project or plan a new website.
At La Teva Web we work on both maintenance and web development, so we can handle either situation. What matters is understanding the state of the project before recommending a solution.
The recent PHP alert is a reason to check your website's security. But it can also be a good opportunity to make sure your website's technology still meets your business's needs.
If you're not sure whether it's up to date, have doubts about its security or have been thinking about redesigning it for a while, we can help you work out what it needs.

Hello! drop us a line
Your website can work perfectly and still have been exposed for years. Two critical PHP flaws open your server to attackers. Do you know if you're safe?