PHP2SHELL SECURITY ADVISORY · OCTOBER 22, 2026

PHP2Shell puts business websites at risk.

Critical PHP flaws can put business websites, customer portals and vendor applications at risk. Discover your potential PHP2Shell exposure with a free assessment from Sollucio.

A focused initial review. Clear priorities for your next step.

Critical severity: CVSS v4.0 9.2Vulnerabilities: CVE-2026-109618 · CVE-2026-109619Priority: Confirm and remediate exposure

UNDERSTAND THE EXPOSURE

PHP may be running
in more places than you think.

PHP2Shell affects PHP itself. A familiar application or managed hosting service can still depend on a vulnerable runtime.

01 / PUBLIC WEBSITES

Websites & online stores

WordPress, Drupal, Joomla and commerce platforms may depend on PHP beneath the application you update.

02 / BUSINESS APPLICATIONS

Portals & internal tools

Customer and patient portals, wikis, help desks and custom applications may create less visible dependencies.

03 / THIRD-PARTY SERVICES

Hosting & vendor systems

Ask providers which services use PHP, who owns remediation, and what evidence confirms the fix is live.

Exposure depends on the runtime, configuration and reachable attack paths. An affected product or version alone does not establish that a breach has occurred.

YOUR IMMEDIATE PRIORITIES

Find it. Fix it. Verify it.

01

Find every PHP dependency.

Start with internet-facing services. Include hosting accounts, portals, containers, internal applications and vendor products. Confirm the runtime serving web requests.

02

Patch and activate the fix.

Apply the security release or a vendor-confirmed backport covering both CVEs. Restart affected workers, or rebuild and redeploy containers. Confirm every instance is updated.

03

Verify the result and record ownership.

Validate the running build, test application functions, document remaining exceptions and investigate suspicious activity. Get written patch evidence from your providers.

PHP 8.58.5.12
PHP 8.48.4.27
PHP 8.38.3.36
PHP 8.28.2.35

Security releases issued October 21, 2026. Use these versions, later security releases, or a vendor-confirmed backport. Temporary controls reduce specific attack paths; they do not replace patching. Check current vendor guidance.

FREE PHP2SHELL EXPOSURE ASSESSMENT

Discover your exposure.
Know what to do next.

Not sure where PHP runs or whether your provider has addressed it? Bring us your website, hosting or application questions. We’ll help you focus on the gaps that deserve attention.

  • 01Identify likely PHP dependencies.
  • 02Review patch status and available evidence.
  • 03Prioritize practical next steps.
A focused initial review, with scope agreed before work begins. Active testing, remediation and incident response are separately scoped.

LET’S FIND YOUR NEXT STEP

Start with a conversation.

Email our cybersecurity team to request your free PHP2Shell exposure assessment. Include your company name, website and a brief description of the systems you’d like to discuss.

security@solluciopartners.com

We’ll agree the scope of the initial review with you before work begins.

QUESTIONS BUSINESS LEADERS ARE ASKING

Get clarity before you assume.

My website provider manages updates. Am I covered?

Ask your provider to confirm the PHP runtime version or backport, whether both CVEs are addressed, and whether all workers, images and replicas have been updated. Application updates and runtime updates may be managed separately.

Does an affected version mean we have been breached?

No. A vulnerable version establishes potential exposure, not proof of compromise. Review suspicious files, processes, accounts and outbound connections. Signs of compromise warrant a separate investigation.

What if we cannot patch immediately?

Escalate the exception and follow current vendor-specific guidance. Restrict access and apply relevant WAF protections where appropriate. Interim controls address specific attack paths and do not make every unpatched installation safe.

What does the free assessment include?

A focused initial review of likely PHP dependencies, available patch information and practical priorities. We agree the scope before work begins. Active testing, remediation and incident response require a separate scope.

SHARE WITH YOUR TEAM

A clear plan for your
next security conversation.

The three-page business advisory includes fixed PHP versions, response priorities and five questions to ask your hosting provider.

Download the business advisory

Technical guidance reviewed October 22, 2026. Primary sources:

Clear exposure. Practical priorities. An accountable partner.

Get your free assessment