Read time: 7 minutes
In short: Usually more than one party, though one provider can cover several parts. Your hosting company, your website developer and the companies behind your software may each handle different updates. But publishing an update is not the same as installing it, testing it and making sure your website still works. Who does that depends on your hosting plan and maintenance agreement. If no one can tell you who is responsible, don't assume the work is being done. Here's who usually handles each part of a website, four common assumptions to check and five questions to ask.
What did the November 2026 Microsoft 365 outage show about software updates?
It's a reminder that software can work for months before a hidden problem surfaces, and that when something goes wrong, the next question is who is responsible for fixing it. Starting around midday Eastern on Thursday, November 12, 2026, an outage interrupted Microsoft 365 services including Outlook, and many users couldn't send or receive email into Friday, the Associated Press reported. Microsoft executive Charles Lamanna said on November 16 that a hidden defect in an update rolled out in July was one of three contributing factors. That update had been deployed worldwide for more than three months without impact, People reported. Microsoft's explanation is preliminary, with a final review to come.
A Microsoft outage and a WordPress or Drupal update are different things, but the lesson carries over: a change can look stable for months, and someone has to investigate and respond when it fails. If your website sends contact-form notifications to an Outlook inbox, an email outage can delay those notifications or keep them from reaching you. Whether the original inquiry is still saved depends on how your form is set up, so check that submissions are also stored somewhere you can reach without email.
Who is responsible for each layer of software behind a website?
One company may handle several layers of your website, or the work may be split among your host, developer and software vendors. What matters is knowing who installs, tests and monitors each update. Use this seven-part checklist to compare those responsibilities with your hosting plan and maintenance agreement.
| Layer | What it does | Who usually updates it | What to confirm |
|---|---|---|---|
| Domain name and DNS | Points your web address to your site | Nothing to patch, but someone has to renew the domain and make DNS changes. That's whoever holds the registrar and DNS logins, which should be you and is sometimes the agency that built the site | Your business controls the registration and auto-renew is on |
| Hosting server, operating system and SSL certificate | Runs the machine your site lives on and encrypts traffic | The hosting company on shared and managed plans, though what's included varies by plan; you or your developer on an unmanaged server | Whether your plan is managed or unmanaged, which updates it lists, and who watches certificate renewal |
| PHP | The language WordPress and Drupal run on | The host offers versions, and someone has to choose one and test the switch. Some hosts move sites off a retired version on their own schedule | Which version you run and who decides when to change it |
| CMS core (WordPress or Drupal) | The system you log in to and edit | The project publishes updates. WordPress can install core updates automatically, depending on how the site is set up. Drupal core updates are applied by an administrator or maintenance provider. Confirm your actual settings and who tests the site afterward | Whether major version upgrades are covered |
| Plugins, modules and themes | Add features and design | Each maker publishes updates. In WordPress, automatic plugin and theme updates stay off until someone turns them on, so your developer or maintenance provider installs and tests them | Who checks for plugins their makers have abandoned |
| Custom code | Anything built only for your site | The developer or maintenance team currently contracted to support it, which may not be the original builder | Who can change it today |
| Connected services (email, forms, payments, analytics tags) | Deliver leads, take payments and track visits | The vendor maintains its own platform. Your developer or maintenance provider may need to update the plugin, API key or tracking code that connects your site to it | Which services your site depends on and how you'd know if one failed |
What do website owners most often get wrong about updates?
They assume another party has a layer covered. Four assumptions cause most of the gaps:
- "My host handles it." A standard hosting plan covers the server, not the plugins and code installed on it. Patchstack, a company that sells WordPress security tools, tested hosting companies' defenses in 2025 and reported that 26% of vulnerability attacks were blocked.
- "WordPress updates itself." Only in part. Minor core releases install automatically by default, and sites first installed on version 5.6 or later do the same for major releases, but plugin and theme auto-updates are opt-in. Patchstack counted 11,334 new vulnerabilities in the WordPress ecosystem in 2025 and found 91% of them in plugins.
- "Updating WordPress updates PHP." It doesn't. PHP is set at the server, which is why a fully updated WordPress site could still be exposed to PHP2Shell, the critical PHP vulnerability disclosed in October.
- "The company that built my site maintains it." Only if a maintenance agreement says so. A build contract that ends at launch leaves no one assigned.
Which website software deadlines fall in December 2026?
Two, and both have published dates. A third date comes sooner.
| Software | Date | What ends | Source |
|---|---|---|---|
| Drupal 10 | December 9, 2026 | All new releases of Drupal 10 | Drupal core release schedule |
| PHP 8.2 | December 31, 2026 | Security fixes from the PHP project | PHP supported versions |
There's also a more immediate Drupal update. The Drupal Security Team has announced critical security releases for every supported version of Drupal (10.6, 11.3 and 11.4), due Wednesday, November 18, 2026, between noon and 4 p.m. Eastern. It says at least one of the vulnerabilities can be exploited by anonymous users and that exploits might be developed within hours or days. If your site runs Drupal, confirm who is responsible for applying that release promptly.
Neither December date switches a website off. The site keeps running, and the project behind the software stops patching it. Two details change the urgency for Drupal sites. Drupal 10.5 and older already lost security support in the week of June 29, 2026, so only version 10.6 is covered until December. Drupal 11.3 loses security support in the week of December 7, so an upgrade should land on Drupal 11.4 or newer. For PHP, our guide to PHP 8.2 end of life covers how to check your version and what an upgrade involves.
All three dates are known in advance. The important step now is confirming who will plan, test and complete the work.
What should you ask your host and developer?
Ask five questions and get the answers in writing. One email to your host and one to your developer or agency is enough to start.
- Who installs updates, and how often? Get a name for each layer: PHP, the CMS, plugins and custom code.
- Is my hosting managed or unmanaged, and what's on the list? Managed plans differ, so ask which updates are included. An unmanaged plan leaves the server to you.
- How are updates tested, and what is the recovery plan? Ask whether changes are tested on a staging site where appropriate, whether backups are available, and whether restoring from one has been tested.
- How will I hear about a critical vulnerability? A good answer names who contacts you and how soon.
- Who controls the accounts and access? Confirm that your business controls its domain registration, can recover hosting and CMS administrator access, and knows who has permission to make changes.
If an answer is "I'm not sure," or your host and developer give different answers, ask them to agree in writing on who is responsible before an urgent update is needed. Microsoft's July update is why the third question matters. It went through Microsoft's deployment process with no issues observed and still failed in November.
Not sure who updates the software behind your website? MOJO Creative Digital builds and maintains websites on WordPress and Drupal. We can tell you which versions your site runs and what needs attention. Request a quote or call us at (410) 439-1994.
Frequently Asked Questions
Does my hosting company update my website?
Partly. On shared or managed hosting, your host usually maintains the underlying server, but exactly what that includes varies by plan. Some managed WordPress services also handle core, plugin or theme updates. Ask which updates are included, whether they are tested, and who responds if something breaks.
Does updating WordPress also update PHP?
No. WordPress core, plugins and themes update inside the WordPress dashboard, and PHP is set at the server through your hosting account. A site can show every WordPress update as complete and still run a PHP version that no longer gets security fixes. To check yours, go to Tools, then Site Health, then the Info tab, and open Server.
Who is responsible if a website update breaks something?
Start with your hosting and maintenance agreements. They should explain who installs and tests updates, who restores the site if something breaks and what response times apply. If those duties are unclear, responsibility may be disputed and repairs may require a separate agreement or charge.
What does a website maintenance plan cover?
There's no standard plan, so check yours for five things: CMS updates, plugin and theme updates, backups, monitoring and a response time for critical vulnerabilities. Then ask whether PHP upgrades, major version upgrades such as Drupal 10 to Drupal 11, and repairs after a failed update are included or billed separately.