
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
WordPress runs on older PHP than the PHP project still protects, and those two facts are easy to mix up. This guide separates the minimum, the recommended and the actually safe PHP version, using the official WordPress pages. Sources read 22 October 2026.
People say "minimum PHP version" and mean three separate ideas. Mixing them up is how sites end up on old PHP with a clear conscience.
| Word | What it means | Where it comes from |
|---|---|---|
| Minimum | The oldest PHP that WordPress will still run on | WordPress.org requirements page |
| Recommended | The PHP WordPress asks you to use | WordPress.org requirements and update-php pages |
| Safe | A PHP branch that still gets security fixes, at or above the fixed patch | php.net and the branch end dates |
Minimum is about whether WordPress starts. Recommended is about speed and security as WordPress sees them. Safe is about whether anyone is still repairing the PHP underneath. WordPress.org tells you the first two. The PHP project tells you the third.
Two official pages, both read on 22 October 2026, give the numbers.
| Source | Page date | What it says |
|---|---|---|
| WordPress.org requirements | Last modified 7 May 2026 | Recommended PHP 8.3 or newer. Recommended MariaDB 10.11 or newer, or MySQL 8.0 or newer. HTTPS support required. Apache or Nginx preferred. Also runs on PHP 7.4 and MySQL 5.5.5 or newer, but those have reached end of life and may leave a site open to security risks |
| WordPress.org, update PHP | Read 22 October 2026 | Recommends PHP, currently 8.3 or higher, as faster and more secure. WordPress works with PHP as far back as 7.4. Test themes and plugins on newer PHP. If Site Health shows 8.3 or higher, no update is needed on its advice |
Notice the wording. WordPress.org itself calls 7.4 end of life on the requirements page. So even the minimum is labelled as a risk.
WordPress keeps a developer page called PHP Compatibility and WordPress Versions on make.wordpress.org. It was last updated 19 August 2026, per the page. It marks each pairing with Y for supported or N for not supported. It says WordPress software is tested and compatible with the versions listed, and that it dropped the old "beta support" label in May 2026.
Here is a short extract of the current table. We have kept the columns that matter most to site owners.
| WordPress | PHP 8.5 | PHP 8.4 | PHP 8.3 | PHP 8.2 | PHP 8.1 | PHP 8.0 | PHP 7.4 |
|---|---|---|---|---|---|---|---|
| 7.1 | Y | Y | Y | Y | Y | Y | Y |
| 7.0 | Y | Y | Y | Y | Y | Y | Y |
| 6.9 | Y | Y | Y | Y | Y | Y | Y |
| 6.8 | N | Y | Y | Y | Y | Y | Y |
| 6.7 | N | Y | Y | Y | Y | Y | Y |
| 6.6 | N | N | Y | Y | Y | Y | Y |
| 6.5 | N | N | Y | Y | Y | Y | Y |
| 6.4 | N | N | Y | Y | Y | Y | Y |
Source: make.wordpress.org, PHP Compatibility and WordPress Versions, page updated 19 August 2026. The page lists older WordPress versions too, with older PHP branches.
Three things to take from it.
The compatibility table answers one question: does WordPress run on this PHP? It does not answer the question that matters for security: does the PHP project still fix this PHP?
On 21 October 2026, php.net announced fixes for two critical remote code execution flaws in a corrected release of its branch. It also said PHP 8.1 and older no longer receive updates from the PHP project, though it gave minimal source backports for 7.4, 8.0 and 8.1, and some Linux vendors got patches in advance. For the full story, read our main guide to the PHP vulnerability of October 2026.
Now compare that with the table above. WordPress 6.4 through 7.1 are all marked Y on PHP 8.0 and 7.4. Yet those PHP branches are past the PHP project's own support. So a site can be fully "supported" by WordPress and still sit on a PHP branch with no regular fixes.
Kinsta's PHP page, updated 8 June 2026 and citing endoflife.date, gives the branch dates.
| PHP branch | Status per Kinsta (8 June 2026) |
|---|---|
| 8.5 | Active support to Dec 2027, security to Dec 2029 |
| 8.4 | Active support to Dec 2026, security to Dec 2028 |
| 8.3 | Security fixes only, to Dec 2027 |
| 8.2 | Security fixes only, to Dec 2026 |
| 8.1, 8.0, 7.4 | End of life |
Kinsta says nearly half of WordPress sites still run an end-of-life PHP version. That is their claim, and we have not checked it ourselves. Our post on PHP end of life dates goes deeper on these dates.
Put the three layers together.
PHP 8.2 passes today but its security support is listed as ending in December 2026, so it is a poor place to settle. If your plugins allow it, 8.3 or 8.4 is the sensible target, and 8.5 once your WordPress version and plugins support it. Kinsta calls 8.4 the safer default.
Do not forget the other half of the stack. WordPress.org recommends MariaDB 10.11 or newer, or MySQL 8.0 or newer, and requires HTTPS support. Ask your host about those at the same time as PHP.
Read your PHP version from the Server block on the Info tab of Site Health. Our guide to checking your PHP version in WordPress, cPanel and the command line shows other routes, and the guide to checking and updating PHP on WordPress walks through the backup, plugin check and switch. If your host controls the version, send the questions from our guide on what to ask your web host.
If a plugin or theme will not run on a newer PHP, treat that as the real finding. The cost of replacing it is usually smaller than the cost of staying on a branch that nobody repairs. See our post on WordPress website cost for how upkeep fits into the yearly picture.
We build and look after WordPress sites, and PHP, plugin and theme updates sit inside our maintenance work, always with a backup and a test first. You can read about WordPress development and Webflow maintenance. Some owners decide they would rather not manage servers at all, and Webflow migration moves a WordPress site across while keeping its addresses. We price from scope, never by the hour. This post is general information, not a guarantee of safety or legal advice.
WordPress.org says it runs on PHP 7.4 or newer and recommends PHP 8.3 or higher. It also notes that 7.4 has reached end of life. So 7.4 is the floor, not a good choice.
PHP 7.4, according to the WordPress.org requirements page, last modified 7 May 2026. Treat it as the point where WordPress stops working, not as a safe setting.
It works with the current WordPress versions in the official table, and php.net fixed it in 8.2.35. But Kinsta lists its security support as ending in December 2026, so plan to move to 8.3 or 8.4.
Not always. The official table marks older WordPress versions as not supported on newer PHP, and WordPress 6.8 and 6.7 are not marked supported on PHP 8.5. Update WordPress first, then raise PHP.
No. WordPress support means the software runs. It does not mean the PHP project still fixes that branch. Check the branch dates and your patch number as well.
Open the Info tab in Site Health and look at Server. If you cannot log in, your hosting panel or your host can tell you.
WordPress.org said no WordPress update is required for them, because they are PHP flaws and not WordPress flaws. The fix is a newer PHP at your host. Updating WordPress is still useful if you want a newer PHP branch to be supported.

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.

A WooCommerce shop runs on PHP, so the October 2026 PHP fix matters. What to check, what to ask your host, and how to update PHP without risking checkout.

What a website redesign costs in 2026: ranges from ten published guides in USD, AUD and GBP, why they disagree, and a sheet to make quotes comparable.