Some companies see cybersecurity as a cost center. We see things a little different. LEARN MORE >

Our seasoned Chief Information Security Officers bring strategic guidance to your leadership team, helping you right-size your cybersecurity operations.


A full suite of manage solutions from our US-based Security Operations Center (SOC)—staffed 24x7x365 by a full team of experienced analysts.


You can count on our IR team to contain the damage from a cyberattack, investigate the origins of the breach and build better protections for the future.


Why Inversion6

With an abundance of solutions and providers, the task of choosing the right option is critical and can sometimes be overwhelming.

Contact Us

Explain It to a Marketer

Is Your WordPress Site at Risk?
PHP2Shell Explained

Two critical PHP flaws went public on October 21. Attackers started testing them almost immediately. If your website runs on WordPress, Drupal, Joomla or Magento, your website team needs to know what happens next.

In this episode of Explain It to a Marketer, Inversion6 breaks down PHP2Shell in plain English: what it is, why it matters to the team that owns the website and the four questions to bring to IT today.

PHP2Shell is a pair of critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) that can let attackers take over WordPress, Drupal, Joomla and Magento sites without a login, and Inversion6 helps organizations close the gap with managed detection and response, penetration testing and incident response.

PHP Freak Out thumbnail for Explain It to a Marketer, the Inversion6 video that explains the PHP2Shell vulnerability and what it means for WordPress website owners

Watch the Episode

PHP2Shell, Explained in Plain English

Prefer to read? Inversion6 pulled the key points and the four questions for IT into this page. Watch on YouTube

What Inversion6 Covers in This Episode



01

What It Is

Two critical flaws in PHP, the language that runs most of the web.



02

Why It Matters

One crafted request can hand an attacker your web server. No login required.



03

What to Ask IT

Four questions that get your website patched and protected today.

The Short Version

What Is PHP2Shell?

PHP2Shell is the name for two critical vulnerabilities in PHP, the programming language behind WordPress, Drupal, Joomla and Magento. An attacker can send one crafted request to an unpatched server and run their own code on it. No username. No password. The fix is to update PHP itself to a patched version.

Wiz Research found the flaws with help from frontier AI models and disclosed them on October 21, 2026, the same day PHP shipped patched releases (8.5.12, 8.4.27, 8.3.36 and 8.2.35). Wiz Research estimates PHP powers about 70% of websites. The two CVEs carry severity scores up to CVSS 9.2, and every PHP version released in the last decade is affected, going back to PHP 5.4. Beyond taking over a server, the flaws can expose server memory that may hold passwords, session tokens and API keys.

Here is the part marketers need to hear: your site can be fully up to date and still exposed. Updating WordPress or a plugin does not update PHP. PHP lives on the server, managed by IT, your agency or your hosting provider. That is why Inversion6 pairs application security reviews with autonomous penetration testing to confirm the patch holds and managed detection and response to watch for exploit attempts around the clock.

In One Sentence

PHP2Shell is a pair of critical PHP vulnerabilities (CVE-2026-109618 and CVE-2026-109619) that can let attackers take over WordPress, Drupal, Joomla and Magento sites without a login, and Inversion6 helps organizations close the gap with managed detection and response, penetration testing and incident response.

Why It Matters

Why PHP2Shell Is a Marketing Problem, Too

Your Site Becomes Their Site

Remote code execution means an attacker can deface pages, plant malicious redirects or use your server to attack your visitors. Your brand is the one on the URL.

Your Data Walks Out the Door

Leaked server memory may include passwords and the API keys that connect your site to your CRM, marketing automation and analytics tools.

Your Search Rankings Take the Hit

Search engines flag and demote compromised sites. Cleanup takes days. Rebuilding trust with search engines and customers can take much longer.

Inversion6 runs a 24/7 security operations center that watches for this kind of activity, and Inversion6 dark web monitoring can alert you if stolen credentials surface. Not sure where your exposure starts? A cybersecurity risk assessment gives you the full picture.

Bring These to IT Today

The Four Questions to Ask About PHP2Shell

You do not need to patch a server to protect your website. You need clear answers from whoever does. Inversion6 recommends starting with these four questions.

Why it matters: PHP2Shell lives in PHP, not in WordPress or your plugins. The patched releases are 8.5.12, 8.4.27, 8.3.36 and 8.2.35.

A good answer: A specific version number and the date it was last updated. Anything on PHP 8.1 or older is end of life and needs an upgrade plan, not just a patch.

Why it matters: Marketing often owns the website while IT, an agency or a hosting provider owns the server. The gap between those teams is where patches get missed.

A good answer: One named owner, a confirmed patch date and a plan for the next critical update.

Why it matters: Patching can take time, especially on older sites with custom code. A web application firewall can block known exploit attempts in the meantime.

A good answer: Confirmation that a web application firewall is active with a rule for PHP2Shell in place. Treat it as a stopgap, not a fix.

Why it matters: Exploit attempts started quickly after disclosure, and attackers can read memory that may hold passwords and API keys.

A good answer: Someone has reviewed server logs for unusual errors, checked for unexpected files or admin accounts and rotated the credentials the site uses. If anything looks off, bring in Inversion6 incident response.


Not Sure Who Owns Your Patching?


PHP2Shell FAQ

PHP2Shell Questions, Answered

PHP2Shell is the name for two critical vulnerabilities in PHP itself, tracked as CVE-2026-109618 and CVE-2026-109619. They can let an attacker run code on a web server without logging in, and they can expose server memory that may hold passwords, tokens and API keys. Wiz Research disclosed the flaws on October 21, 2026, the same day PHP released patched versions.

Yes, if your WordPress site runs on an unpatched version of PHP. The flaw sits in PHP, the language WordPress is built on, so a fully updated WordPress install and clean plugins do not protect you on their own. The same is true for Drupal, Joomla, Magento and other PHP-based sites.

No. Updating WordPress updates the application, not the PHP version running on your server. PHP is updated by whoever manages your hosting: your IT team, your web agency or your hosting provider. Ask them to confirm the PHP version directly.

PHP released 8.5.12, 8.4.27, 8.3.36 and 8.2.35 on October 21, 2026 to address PHP2Shell. Sites on PHP 8.1 or older run end-of-life versions that do not receive an official fix, so they need an upgrade to a supported version.

Yes. Amazon Threat Intelligence has reported broad exploitation in the wild, and public proof-of-concept exploit code appeared soon after disclosure. Treat patching as urgent, not routine.

Bring four questions to IT: what PHP version the site runs, who owns patching, what protects the site while it is patched and whether anyone has checked for signs of compromise. Inversion6 can help answer any of them through managed detection and response, penetration testing and incident response.

Inversion6 helps organizations confirm their exposure, block exploit attempts and recover if something got through. Inversion6 managed detection and response monitors servers 24/7, autonomous penetration testing verifies that the patch held and the Inversion6 incident response team steps in at the first sign of compromise.

Eliminate Reactive

Get Ahead of the Next PHP2Shell

Connect With Us

Get a Second Set of Eyes on Your Website

Tell us what your site runs on and who manages it. An Inversion6 expert will help you confirm your PHP2Shell exposure and map out next steps. Experiencing a breach right now? Go to emergency incident response.

Read Along

Episode Full Transcript:

Explain It to a Marketer, Episode 1. Nick Worner talks with Josh Fenton, VP of Security Services at Inversion6, about AI-discovered vulnerabilities and PHP2Shell.

Nick Worner

Hi, I'm Nick Warner. Welcome to the very first episode of TRG's Explain It to a Marketer. In this recurring series, we talked to one of our many subject matter experts at both TRG and Inversion 6 and asked them to break down their topics in terms so simple that even a member of the marketing team can understand. In this episode, we talked with Josh Fenton, VP of Security Services at Inversion 6. We asked Josh to join us to break down the rise of AI discovered cybersecurity vulnerabilities, specifically a recent vulnerability within PHP that freaked out the entire internet.

Enjoy the episode. Josh Fenn, VP of Security Services. Welcome to the very first episode of Explain It to a Marketer. You're our first guest.

Josh Fenton

Yeah. Thanks Nick. I'm happy to be here.

Nick Worner

Great, great. So what we call Jennyer for today is we need some help explaining it to a marketer regarding this PHP drama that we all read about at the end of last week. And I'm gonna be honest with you, PHP sounds like some kind of drug to me. I don't know anything about it. So let's start with that. What is it and what what are we all worried about here?

Josh Fenton

Yeah, so I mean I think the most simple way to explain what PHP is, is it's a programming language. So it is kind of the the glue behind a lot of internet applications. Very easy to, you know, translate data or databases into visual format. It's used by about 70% of websites that kind of exist out on the internet. So, you know, if you talk about you know, major telecommunications providers or, you know, streaming video game services or things like WordPress or Magneto, which are like carts or websites that are developed kind of by smaller organizations or small businesses, that all runs with some, you know, piece of that PHP library within it.

Nick Worner

And my understanding, if I read the stories correctly, is that this AI discovered this vulnerability. Yes, this is something that was kind of laying there for years and nobody noticed.

Josh Fenton

Yeah, I mean, people have been trying to get rid of a programming language like PHP since nineteen ninety-five, right? Hey, learn this new thing. You know, this thing's antiquated. But again, it's easy, it works, so it's out there. So I think we are living in a a new world when it comes to vulnerabilities. And, you know, AI just moves so much faster than a human can. And I think, you know, whether it's, you know, the intention is good or the intention is bad, you know, AI has the ability to go through these programming languages, go through applications at such a rapid rate that this is probably our new normal for vulnerability disclosure.

Nick Worner

Got it. Now here's what we're really gonna press you with explain it to a marketer because I'm gonna ask you what this vulnerability actually does. And you have to keep in mind how little I understand about programming languages.

Josh Fenton

Yeah, sure. So once the vulnerability was made aware, right? And AI and you know, there's multiple different websites from security news, and even I saw it, you know, on Yahoo and CNN, right? Once a vulnerability is out in the wild, that's where people then can write exploits against that vulnerability. For this vulnerability in particular, a exploit was written called PHP 2 shell. And what that basically means is I was able to launch a programmatic attack, let's say at a WordPress website, that would then give me shell access. And what us nerds, right, would call shell access is basically the ability to manipulate the back end of those websites and basically take control of it.

Nick Worner

So if the internet wasn't working properly for me last week, is that what's going on here? Has this actually hit ground in some places?

Josh Fenton

Yeah, most likely. I mean there while organizations are, you know, slow to admit that they're using incredibly dated you know programming languages, they are. Everybody does. So, you know, there were some major, as I mentioned earlier, some major telecommunications providers. One of the most popular video game companies had it took their site offline. Now, none of them said it was because of PHP, but you know, I think that you know, we can maybe make some assumptions there.

Nick Worner

Got it. Okay. It's good to know. So like you mentioned, this is kind of broken into mainstream news. You know, I got this in my news feed. So explain it like how much do I personally need to be freaking out about this versus a company level people who are building sites? Like help me understand that a little bit.

Josh Fenton

Yeah, so I mean if you're a small business, you know, and you're selling things on, you know, a WordPress website or a Magneto website, or even potentially on, you know, some of the larger kind of co-managed selling sites, I think you should be concerned. You know, I think you should probably reach out to, you know, if your buddy Bob is managing your personal website for whatever trinkets you might be selling, or maybe you're using a larger enterprise like a WordPress site, you know, I think you should probably reach out to who's where that's hosted and who's managing it, and just make sure that you know that it's fully patched and that you're secure and safe. And make sure you get that back in documentation as well. You know, if you're a large enterprise, you know, this is just the next vulnerability in the long list of vulnerabilities that you know might be sitting within an organization. And while no tool can solve that, knowing what assets you have in your network, what applications, what systems in your network, having good asset management is a foundational control to solving that. At inversion six, we actually have a tool. We call it tarot, you know, like the like the cards, right? Which is going to help you read your risk. And what it does is it takes all of that asset information, it matches it against the national the national vulnerability database that produces and categorizes all vulnerabilities.

And then it basically can tell you at what stage in kind of the risk lifecycle your organization is at for a vulnerability like PHP. So, you know, a you know, someone in charge can say, hey, where are we? And the tool within three clicks can say, Hey, actually we've patched it at, you know, at 95% of our endpoints, but there's this five percent and the the tickets with Sue and the roadblock is X.

And but it's going to be solved, right? So it's kind of a tool that looks at the entire risk exposure lifecycle and really pinpoints where it exists in your environment and it answers the four questions of where is it, what version, who owns it and you know, what do I need to do to solve it?

Nick Worner

Got it. So what I think I'm hearing you say is that you can prepare or assume to prepare for more things like this because this will not be the last thing like this that we see. And and basically get get ready because it's coming.

Josh Fenton

I think so. I think last week with all not just PHP, but Node.js, Java, there was a couple large enterprise firewall vulnerabilities as well. I think this is our new normal. I think with AI assisted vulnerability detection, I think that we're expecting this to kind of be what happens every single week. Now, I as a security practitioner for over twenty five years now, I love this. I think this is exciting.

And you know, jokingly I kinda looked at my staff and said, If this isn't fun for you and this isn't why you're here, maybe you should think about going to cut lawns for your for a living. Or go into marketing. No.

Nick Worner

That hurts, but it's very, very true. I'm glad you're excited. I'm glad somebody is. I'm a little less freaked out than I was before. So thank you. I think you actually have successfully explained this to a marketer. I certainly know more than I did before. And I think everybody more importantly who needs to be worried about this has a little more of an understanding about what to do. So I really appreciate it. I think we'll call that a successful first episode of Explain It to a Marketer. So thanks for making the first one a good one.

Josh Fenton

Yeah, thank you. Thanks for having me and I look forward to future episodes. This was really fun.

Nick Worner

Great. Take care, Josh.

Josh Fenton

You too.

Back to the video