Black Friday: 7 Last-Minute Checks for Your WooCommerce Store
Black Friday is days away. Here are the 7 checks we run on every WooCommerce store before Friday, plus what you shouldn't touch this week.
Read more →A critical Apache flaw (CVE-2026-119618, 9.8 out of 10) can't be fixed by updating WordPress. Here's what happened and the five questions to send your hosting provider today.
Updating WordPress doesn’t fix this, because the flaw isn’t in WordPress. It’s in Apache, the web server that delivers your site to every visitor before WordPress even gets involved. If your site runs on Apache, this is a conversation to have with your host today, not next week.
On November 11, 2026, a critical vulnerability in Apache httpd was disclosed, tracked as CVE-2026-119618 and rated 9.8 out of 10. It’s an unauthenticated remote code execution in Apache’s HTTP/2 module (mod_http2), caused by memory corruption in the assign_headers() function. In plain terms: an attacker with no account can run code on the server.
The flaw affects Apache 2.4.55 through 2.4.70, and only where HTTP/2 is enabled (with the h2 or h2c protocols). Servers that only use HTTP/1.1 aren’t affected. The fix was released the same day, in Apache 2.4.71.
Think of your site as a building. Apache is the front door: it receives every visit, negotiates the connection (HTTP/2 included), and then hands the request to WordPress, which builds the page. The flaw is in that door, in the way Apache processes HTTP/2 headers, before WordPress runs a single line of code.
Updating WordPress, your theme, or your plugins doesn’t touch the server software. Neither does switching themes or installing a security plugin. The only way to close this flaw is to update Apache to version 2.4.71, and only your hosting provider or the server administrator can do that.
As of November 12 there was no confirmed exploitation in the wild, and the flaw wasn’t listed in CISA’s KEV catalog. That’s good news, but it isn’t a guarantee. Red Hat notes that research has already demonstrated reliable exploitation against a server with the default configuration, and that a public reproduction lab exists. In other words, the path to exploiting it is known and has been walked, even if nobody has seen it in real attacks yet.
On top of that, the fix has existed since November 11, but distribution packages were still lagging as of November 12. Version 2.4.71 existing doesn’t mean your server has it installed. So the right question isn’t whether a patch exists. It’s whether your server already has it.
Copy these questions and send them to your hosting provider:
How to read the answers: if your server doesn’t use HTTP/2, you’re not affected. If it already runs 2.4.71 or later, you’re fixed. If it runs a version between 2.4.55 and 2.4.70 with HTTP/2 enabled, you need the update now. And if your provider doesn’t know which version it runs, or doesn’t answer, that silence is an answer too: it’s time to review your hosting.
Most business owners never ask what software their site runs, and generally they have no reason to. But when a critical server flaw shows up, that question is the difference between being protected and not knowing.
At MD3 Digital Solutions we manage high-performance hosting for our clients: we check the Apache version, apply the update, and verify the fix is active. If you don’t know which version your site runs, contact us and we’ll check it for you.
Black Friday is days away. Here are the 7 checks we run on every WooCommerce store before Friday, plus what you shouldn't touch this week.
Read more →
WooCommerce 11.3.0 and a Stripe Gateway security fix shipped on November 11. Here's what's new, what the Stripe update closes, and an 8-step checklist before Black Friday.
Read more →
WooCommerce 11.2.2 shipped on November 4, 2026 as a security release. Here's what it fixes, what changes in your store, and a step-by-step way to update without losing orders.
Read more →AI assistant — answers may be inaccurate.