Your Website Builder Got Patched. Did the Server Under It?

It's a Thursday afternoon. Your business manager forwards a headline with one line on top: "Does this affect us?" The headline has words like "critical," "remote code execution," and a nickname, "php2shell." Nobody in the front office knows what PHP is, and the person who built the website moved on two years ago.
If that email landed in your inbox last week, take a breath. This is a two-minute check, not an emergency drill.
Quick answer
If your school or nonprofit website runs on WordPress or Drupal, it runs on PHP. PHP released security fixes on October 21, 2026. You don't need a WordPress or Drupal update for this. What you need is a short reply from your web host confirming your site's PHP version and that it was updated after October 21. Then test your forms.
What happened, in plain language
PHP is the engine under WordPress, Drupal, and many other website builders. Your theme and plugins are the car body; PHP is what makes it go. Hosting companies usually install and maintain that engine on their servers.
On October 21, the PHP project released fixes for two critical flaws that, in its words, "can allow unauthenticated remote code execution." The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35.
Calm context before you worry
- No WordPress update is needed. WordPress.org says: "No WordPress update is required or planned for these issues."
- Drupal points to your host. Drupal's security team says that if your host manages PHP, you should "follow their communications for timing and any required action."
- Hosts had a head start. PHP says Linux distributions and long-term support vendors received the patches in advance, and WordPress.org notes your host "may already be working to update PHP."
- No attacks seen at publication. The U.S. Cybersecurity and Infrastructure Security Agency (CISA) said it "has not observed successful exploitation of these vulnerabilities in the wild as of the time of publication."
CISA also advises that organizations that can't update right away, or that run PHP 8.1 or earlier, take PHP-based systems offline until they're patched or updated. For most small schools, that decision belongs to your host, so the questions below are how you find out where you stand.
Three questions to ask your web host
Copy these into an email or support ticket. You don't need to understand servers to ask them.
- "Which PHP version is our site on, and was it updated after October 21, 2026?"
- "Are we on PHP 8.1 or older? If so, what's the upgrade plan and timeline?"
- "Who tests our enrollment, tour, and donate forms after a server update?"
Where to look yourself
If you have WordPress admin access, go to Tools > Site Health > Info > Server. The PHP version is listed there. WordPress.org notes that many hosts also show it in the hosting administration panel.
After a PHP upgrade, test your forms
A new PHP version can quietly break an older plugin or theme. The page still loads, but the inquiry form stops sending email. In admissions season, that's the part that costs you families.
- Send a test inquiry through your enrollment or "request info" form. Done when: the notification email arrives in the right inbox.
- Book a test tour if you take tour requests online. Done when: the confirmation reaches both you and the test address.
- Make a small test donation (or use your platform's test mode). Done when: the receipt email arrives and the gift shows up where your team expects it.
The date nobody is watching: December 31, 2026
Here's the quieter part of this story. According to PHP's supported versions page, security support for PHP 8.2 ends December 31, 2026. PHP 8.3's security support runs through December 31, 2027.
If your host tells you you're on 8.2, the October fix still applies, but ask about the next step now, not in the middle of winter break. A version upgrade is also a good moment to retest every form.
Who owns the website?
I spent 14 years running marketing at a community college, and I've worked on both sides of Colorado. The question that mattered most after a tech headline was rarely "are we safe?" It was "whose job is this?" Too often, the honest answer was "the person who built the site," and that person had moved on.
That's a gap, and it isn't anyone's fault. Small schools, charters, and education nonprofits run lean. The website sits between IT, the front office, and the development team, so nobody quite owns it.
That's what monthly Care is for. With Junction's Care plan, someone checks your versions, coordinates with your host when news like this breaks, and tests your enrollment, tour and donate forms after updates. We don't host your site or patch the server. We make sure the people who do have answered the right questions.
What this is not
- This isn't a sign your site was hacked or exposed. It's a reason to confirm a version number.
- It isn't a technical how-to. Server settings and patching belong to your host.
- It isn't a WordPress or Drupal problem. Neither needs a core update for this.
- It doesn't replace your host's own guidance. If they've already emailed you, start there.