Skip to content
Rengie Mendoza
← Insights

Your Website Is Never Finished. Only Maintained.

RMRengie Mendoza ·October 26, 2026·3 min read

Last week, a lot of business owners learned something they never wanted to know: the language their website runs on.

Two critical flaws in PHP, nicknamed PHP2Shell (CVE-2026-109618 and CVE-2026-109619), can let an attacker take over a website's server without ever logging in. PHP powers WordPress, which runs a huge share of small business websites. Fixes shipped on October 21, and attacks are already being reported.

Plenty of owners only heard about it because someone forwarded a scary email. That is the real problem worth talking about.

The "it's done" illusion

A website launch feels like a finish line. The site goes live, the invoice gets paid, and everyone moves on. It is treated like a sign on the building: install it once, then forget about it.

But a website is not a sign. It is closer to the building itself. It runs on software that ages and gets patched. It depends on plugins written by people you have never met, and it lives on a server you have probably never logged into. Leave it alone long enough and it doesn't stay the same. It gets worse.

Trust is the thing at risk

This is not just a tech problem. It is a trust problem.

A hacked site can redirect your visitors to spam, get flagged by Google with a red warning screen, or quietly leak the details people typed into your forms. Your customers will not blame PHP. They will blame you, because your name is on the door.

Every review you earned and every referral a partner sent you ends at that website. When it breaks, all of that trust breaks with it.

What a maintenance routine actually looks like

None of this is complicated. It just has to happen on a schedule, whether or not anyone remembers:

  • Backups that run automatically, and a known way to restore them.
  • Updates to plugins, theme, and WordPress, applied regularly instead of all at once in a panic.
  • Server software like PHP kept on a supported, patched version.
  • Cleanup, removing plugins and themes nobody uses, because the abandoned ones are usually the weak spots.
  • A check after every change, testing that forms, bookings, and payments still work.
  • Someone accountable, a named person, not "the guy who built it a few years ago."

The owners who were fine last week weren't lucky

They already had a routine. For them, PHP2Shell was a checklist item, not an emergency. Someone checked the PHP version, confirmed it was patched, and moved on.

That is what a system does. It turns a crisis into a Tuesday.

If you are not sure where you stand

Start with our step-by-step guide to updating your WordPress site for PHP2Shell. It walks through checking your PHP version, backing up, updating safely, and confirming the patch with your host. If you would rather not touch it, the guide also covers having it done for you.

The takeaway

A website is never finished. It is either maintained or decaying. Decide this week who owns yours, put the routine on a calendar, and the next headline about a critical flaw becomes something you read about, not something you live through.

TrustSystems

Want this working in your business?

Start with the free growth assessment — find your bottleneck in two minutes.

Take the Free Assessment