
Website Design for Australian Small Business (2026)
What a small business website costs in Australia in 2026, with real published prices, plus .com.au rules, GST, hosting, privacy and a hiring checklist.
Website Security
After the PHP news of 21 October 2026, many owners assumed their automatic updates had it covered. They did not, because WordPress updates WordPress, and PHP belongs to your host. This guide shows what updates itself, what does not, who owns each part and where to check. Sources read 22 October 2026.
A WordPress dashboard is full of update notices. It tells you when core, plugins and themes have a new version, and some of that can happen with no click from you. It is easy to turn that into "my site looks after itself".
The catch is where each piece lives. WordPress, your plugins and your theme are files inside your site. PHP is different. It is the engine on the server that reads those files and builds each page. As WordPress.org explains, PHP sits on the server itself. A change therefore happens in your host's settings, or by a request to the host.
Think of a car. WordPress updating itself is like the radio updating its station list. The engine is serviced at the garage, and your host is the garage.
This table uses what WordPress.org says on its pages. Where a page does not cover something, the cell says so, and it does not guess.
| Part | Does WordPress update it for you? | Who owns it | Where to check |
|---|---|---|---|
| WordPress core, minor releases | Yes, background updates are on by default for existing sites, per WordPress.org | You, with WordPress doing the work | Dashboard, then Updates |
| WordPress core, major releases | By default only on fresh installs of WordPress 5.6 or later, per the same page. Otherwise you start it | You | Dashboard, then Updates |
| Translation files | Yes, automatic by default, per WordPress.org | WordPress | Not something most owners need to watch |
| Plugins | Not by default, though each plugin can be set to auto-update from its row on the Plugins screen | You, or whoever maintains the site | Plugins, then Installed Plugins |
| Themes | Generally no, according to WordPress.org's update guide | Whoever looks after your site, possibly you | Appearance, then Themes |
| PHP | No | Your host | Site Health, Info, Server, or the host's panel |
| MySQL or MariaDB | No. The database server is outside WordPress's control | Your host | Your host's panel, or ask the host |
| Web server software (Apache, Nginx and similar) and the operating system | No | Your host | Ask the host |
Sources: WordPress.org developer documentation on upgrading WordPress, WordPress.org's Manage Plugins page, and WordPress.org's "Update PHP" page, all read on 22 October 2026. The database, web server and operating system rows are our reading, not a WordPress.org statement: its requirements page lists them as what WordPress needs from the server, and none of the update pages we read describe WordPress updating them.
A note on the first two rows. The WordPress.org update guide says minor core releases, meaning maintenance and security releases, update on their own by default. Your host or a plugin may change that behaviour, so the dashboard is the place to see what is true for your site.
Recommended on the WordPress.org requirements page: PHP from 8.3 up, plus a database of MariaDB 10.11 or above, or MySQL 8.0 or above. It adds that your host should offer HTTPS, and that Apache or Nginx is the suggested web server.
That page also admits WordPress will still run on PHP 7.4 and on MySQL 5.5.5 or above. Both have reached end of life, though, and the page cautions that they can leave a site open to security holes. That is the trap. WordPress keeps working on an old server, and so the site looks healthy while the PHP under it is not.
For more on the minimum and the recommended versions, read what WordPress requires for PHP. Dates when each version stops getting fixes are in PHP end of life dates and what to do.
It varies a lot, and we will not guess about any single company. Here are the patterns we can describe in general terms, and the question to ask for each.
| What a host might do | What it means for you | What to ask |
|---|---|---|
| Offers a version selector in the control panel | The choice is yours, but nothing changes until you flip it | "Where do I choose PHP, and which is the latest release my plan allows?" |
| Handles PHP upgrades itself on managed plans | The work is theirs, and the schedule is theirs too | "Has my site received the patched PHP release yet, and when?" |
| Does not touch PHP on older plans unless asked | A site can stay on a dated version for years | "What PHP does my plan run today, and can you upgrade it?" |
| Backports security fixes into an old package | The number on screen may look unchanged even though the patch is in | "Please confirm in writing that CVE-2026-109618 and CVE-2026-109619 are fixed on my server." |
WordPress.org mentions that a few hosts may be patching or filtering traffic on your behalf, without naming any. Want ready-made wording? Our questions to send your web host about the PHP security fix can be pasted straight into an email. Why replies differ from plan to plan is covered in our piece on managed WordPress hosting versus shared hosting.
Locked out of the dashboard, or just want a different way in? Our walkthrough for checking your PHP version in cPanel or on the command line has both. Back up first, then follow how to check and update your PHP version on WordPress to make the switch.
Because WordPress keeps its own parts current but leaves PHP to your host, many owners discover the gap only when a headline arrives. Within a day of this advisory we moved several WordPress sites onto a patched PHP version and tested that each one still worked, which closed the gap. Where no one in your team takes that on, the WordPress PHP update gig on Fiverr can handle a one-off update for you. For ongoing care on a different platform, see our Webflow maintenance page. Anyone can read our client reviews on Fiverr and Upwork, and the YouTube channel shows how the work is done.
No. WordPress.org says PHP runs on your website's server and that your hosting company decides which PHP versions your site can use. WordPress can update itself, but it cannot change the PHP under it.
Not because of that setting. That setting covers WordPress files only, while the October 2026 fix is a server-side PHP upgrade. Look up your PHP version in Site Health, then have your host confirm the fix.
It depends on the host and the plan. Some hosts give you a switch, some update on managed plans, and some leave PHP alone until you ask. Ask in writing which version you run and whether the fixed release is live.
No. WordPress.org's plugin guide says you can enable auto-updates for individual plugins from the Plugins screen. That only updates the plugin's own files.
From the dashboard, choose Tools, then Site Health, then the Info tab, and open the Server block. WordPress.org gives this route. Plenty of hosts display it in their control panel as well.
On the database side, WordPress.org suggests MariaDB 10.11 or later, or MySQL 8.0 or later. The database server is run by your host. WordPress does not update it for you. Since the October 2026 flaws sit in PHP, PHP is the urgent part, and the database is something to raise with your host.
Often yes, if your host offers a version switch in its panel. If not, your host can do it for you. Back up the site first, update WordPress, plugins and themes, and test afterwards.
Webflow operates its own servers, and a Trust Center post from 21 October 2026 tells customers there is nothing to do. There is no PHP of yours to update there. This guide is for sites that run PHP, such as WordPress.

What a small business website costs in Australia in 2026, with real published prices, plus .com.au rules, GST, hosting, privacy and a hiring checklist.

Which PHP branch should a WordPress site pick after the October 2026 fixes? Support end dates from php.net, WordPress compatibility notes and plain advice.

Shared hosting, managed WordPress, VPS, agency or freelancer: who picks the PHP version, applies the update, tests the site and confirms it in writing.