Webinar

PHP2Shell: You Patched. Did Your Vendors?

Register

Most teams have patched the PHP2Shell servers they know about. The risk now sits in the ones they don’t: forgotten assets, end-of-life versions, and vendors who haven’t patched. Join UpGuard for a live look at where things stand two weeks on, and how to close it out.

Thanks for attending PHP2Shell: You Patched. Did Your Vendors?! We'll see you at our next event. You can relive the webinar anytime, right here.

Speakers

Greg Pollock

Director of Research and Insights

Craig Deering

Sales Engineer

Event Information

Most security teams have patched the PHP2Shell servers they know about. What’s left is harder: assets nobody remembers owning, end-of-life PHP versions with no fix coming, workarounds that look like fixes, and vendors you’re still waiting to hear from.

In this live 30-minute session, Greg Pollock, UpGuard’s Director of Research and Insights, shares where things actually stand two weeks after the patch, drawing on data from scanning 14M+ companies daily. Craig Deering then shows live how to find, prioritize and close out PHP2Shell across your own attack surface and your vendors, in one workflow in UpGuard’s Risk Operations Center.

We’ll cover how to:

  • Find what you don’t know about: surface PHP on forgotten domains, staging sites and legacy apps, then prioritize end-of-life versions and Apache mod_php servers first.
  • Prove the fix, not just apply it: why mitigations don’t count as fixed, how a rescan confirms an upgrade, and how to handle Linux distributions that backport fixes.
  • Close out your vendors: see which vendors are flagged, rank them by the data and access they hold, and send a remediation request or a short PHP2Shell questionnaire.
  • Cover what scanning can’t see: hidden versions, PHP embedded in products you buy, and your vendors’ own suppliers.

Attendees will leave with a seven-step PHP2Shell checklist and a vendor questionnaire template you can put to work on the same day.