Contact Form 7 “Requires PHP 8.3” Composer Error: Fix It

You updated Contact Form 7, and now the site shows a white screen, “There has been a critical error on this website”, or a bare line of text like this one:
Composer detected issues in your platform: Your Composer dependencies require a PHP version “>= 8.3.0”. You are running 8.2.35.
That’s the exact message from a wp.org support thread, and it’s far from the only one. The CF7 forum has filled up with near-identical posts since early October, one of them titled simply “Why force us to php 8.3“.
What the error means
Contact Form 7 6.2 (tagged on wordpress.org on 6 October 2026) raised its minimum requirements. The readme of every 6.1.x release says Requires PHP: 7.4 and Requires at least: 6.7. From 6.2 on it says Requires PHP: 8.3 and Requires at least: 7.1. The plugin now ships a Composer platform check, a small file that runs as soon as the plugin loads. If PHP is older than 8.3.0, it throws an exception. An active plugin loads on every request, so the whole site goes down, front end and admin.
The plugin author’s reply in that first thread was short: “You are using PHP 8.2.35, which is why you get this error.” So this isn’t a bug that a 6.2.x point release will undo. As of 10 November 2026 the current version is 6.2.4.1, and it still requires PHP 8.3.
Get the site back right now
Your forms are stored in the database, not in the plugin folder. Turning the plugin off doesn’t delete them. Pick whichever of these you can reach first.
- Recovery Mode email. When a plugin causes a fatal error, WordPress usually emails the admin address a “Your Site is Experiencing a Technical Issue” message with a special login link. That link lets you into wp-admin with the broken plugin paused, so you can deactivate it from Plugins. Check spam if you don’t see it.
- Rename the folder. Over FTP, SFTP or your host’s file manager, go to
wp-content/plugins/and renamecontact-form-7to something likecontact-form-7-off. WordPress can’t find it, so it deactivates it. The site comes back, minus the forms. - cPanel or host dashboard. Some hosts (and WP Toolkit in cPanel/Plesk) list your plugins and let you disable one without logging into WordPress. One user in the “Composer detected issues” thread got out this way.
Your contact pages will show the raw shortcode, or nothing, until you pick a fix below.
Fix A: roll back to Contact Form 7 6.1.7
6.1.7 is the last release that runs on PHP 7.4 and WordPress 6.7 or newer. It was tagged in August 2026. In the multisite thread a user wrote “Had to roll back to Version 6.1.7 to resolve the issue”, and that’s the most common fix you’ll see.
Two ways to do it:
- By hand. On the Contact Form 7 “Advanced View” page, scroll to “Previous Versions”, pick 6.1.7 and download it. The direct file is
https://downloads.wordpress.org/plugin/contact-form-7.6.1.7.zip. Delete the renamed 6.2 folder (your forms live in the database, not there), then in WordPress go to Plugins > Add New > Upload Plugin, upload the zip and activate it. If you never renamed the folder, WordPress offers to replace the installed version with the uploaded one. Say yes. - With WP Rollback. The free WP Rollback plugin adds a “Rollback” link to each plugin on the Plugins screen and lists the older versions. It needs a working wp-admin, so on a site that’s already down, use the folder trick above first.
Then stop it from happening again. On the Plugins screen, click “Disable auto-updates” next to Contact Form 7. If your host, ManageWP, MainWP or a similar tool updates plugins for you, pause CF7 there too.
Be honest with yourself about what a rollback is. It’s a holding pattern. You’re pinned to a version the author has moved on from, and we haven’t found any statement that the 6.1 branch will get further fixes. Give it weeks, not years.
Fix B (the real fix): move the site to PHP 8.3
First, check what PHP your site actually runs. In wp-admin go to Tools > Site Health > Info, open the Server section and look at “PHP version”.
Now compare it with the number in the error. They don’t always match. In the multisite thread, the poster said the network runs PHP 8.4, but the log line read “You are running 8.2.34”. Some part of that setup was still served by 8.2. If your host lets you set PHP per domain, per subdomain or per folder, check each one. The version in the error message is the one that counts.
To switch, look in your hosting panel for something like “PHP Selector”, “MultiPHP Manager” or “PHP version”. On many shared hosts it’s a dropdown. If you can’t find it, open a ticket and ask: “Can you move this site to PHP 8.3 or 8.4?” PHP 8.2 gets security fixes only until the end of 2026, so a decent host will have newer versions available already. We covered the same host conversation for WooCommerce in the WooCommerce PHP 8.1 requirement post.
Before you flip the switch on a site that matters:
- Take a backup, files and database. Most hosts have a one-click snapshot.
- Update everything else first, especially your theme and any plugin that hasn’t been updated in a year or two. Old code is what breaks on newer PHP.
- After switching, click around: home page, a post, the contact page (send a real test message), checkout if you have a shop, and wp-admin. Then check the PHP error log or Tools > Site Health for new warnings.
- Know the way back. If something breaks, setting PHP back to 8.2 in the same panel undoes it in seconds. Just keep CF7 on 6.1.7 until you’ve fixed whatever broke.
Once you’re on 8.3 or newer, update CF7 to the current release and turn auto-updates back on. Note that 6.2 also needs WordPress 7.1, so update core too if you’re behind.
When neither fix is possible
Some hosts can’t or won’t move you, and some sites carry an old plugin that dies on PHP 8.3. If you can’t upgrade PHP and don’t want to sit on 6.1.7 forever, the third option is a different form plugin that supports your PHP version. People in the “Why force us to php 8.3” thread said they were moving sites to Forminator or to their theme’s built-in forms.
It’s more work than a rollback: rebuild or import the forms, recheck the emails, test each one. Our Contact Form 7 alternative guide compares the main options.
Check the “Requires PHP” line of whatever you pick, or you end up right back here.
One option that runs on PHP 8.2: Trinity Forms
Full disclosure: Trinity Forms is ours. It’s a form builder that requires PHP 8.2 or newer, so it runs on the PHP 8.2 sites that CF7 6.2 now refuses. It has a free importer for Contact Form 7 forms (Trinity Forms > Import forms, then pick Contact Form 7 as the source), so you can bring your existing forms across instead of building them again from scratch.
The limit is real: Trinity Forms does not run on PHP 8.1 or older. If your host has you stuck below 8.2, it won’t help you, and Fix A or a host move is the better route. The free core is a free download from our site.
Either way, old PHP is a risk of its own (see how many WordPress sites run unpatched PHP).
Frequently asked questions
Is it safe to roll back Contact Form 7?
Yes, for getting a site back up. Contact Form 7 keeps your forms in the WordPress database, not in the plugin folder, so replacing 6.2 with 6.1.7 doesn’t delete them. Take a backup first anyway. The catch is that 6.1.7 is an older release and we haven’t seen any promise of further fixes for that branch, so treat it as a stopgap until you can move to PHP 8.3.
Which PHP version does Contact Form 7 need now?
From version 6.2 onward, Contact Form 7 requires PHP 8.3 or newer and WordPress 7.1 or newer. Version 6.1.7, the last 6.1 release, requires PHP 7.4 or newer and WordPress 6.7 or newer.
Will my forms keep working if I switch PHP?
Contact Form 7 6.2 and newer will only run once PHP is 8.3 or newer, so switching is what makes it work again. The risk is in your other plugins and your theme: old code can break on newer PHP. Back up, update everything first, test on staging if you can, and send a real test message through each form after the switch. If something breaks, you can set PHP back in your hosting panel.