PHP2Shell security update · CVE-2026-109618 / CVE-2026-109619Read the PHP advisory

Patch the risk.
Keep your business running.

PHP2Shell response for business websites and agency portfolios. Get a clear answer, a carefully scoped update, and proof of what changed.

Secure payment with Stripe. We confirm scope and availability before any work starts.

  • Agreed scope & price
  • Application checks included
PHP runtime reviewRemediation summary
Sample
Final status

Patched. Checked.
Documented.

PHP runtime
8.3.358.3.36
  • Security update applied
  • PHP workers restarted
  • Application checks passed
Illustrative exampleSample report

For the PHP you run every day

The vulnerability is in PHP.
The next step is clarity.

A fully updated website can still run on an unpatched PHP runtime. We establish what your web server actually uses, then agree on the right next step.

Understand PHP2Shell

Check the runtime, not just the CMS.

Identify the PHP build serving your application, including separate pools and containers within the agreed scope.

Older numbers can hide newer fixes.

Vendor backports matter. We check package provenance and security advisories, not just a version number.

A patch should come with evidence.

Document the update, confirm restarted processes, and check the application paths your business relies on.

Less uncertainty.
A clear plan at every step.

No changes without an agreed scope.
No handover without a written record.

  1. Verify

    Find what needs attention.

    We review your web runtime and vendor patch status. You get a clear outcome: patched, needs action, or requires more evidence.

  2. Remediate

    Make the right change.

    Agree the maintenance window, prepare a backup and rollback plan, and apply a supported update to the scoped environment.

  3. Confirm

    Know what was done.

    Confirm the running version, test the agreed application functions, and receive a concise change report with any remaining actions.

The right level of help.

Start with one environment.
Scale to your client portfolio.

A clear answer

Verify your exposure

€190 / one-time

Know what needs attention before making changes.

Start with a verification
  • One server, one application
  • Web runtime & vendor patch verification
  • Written findings and a remediation plan
  • €190 credited towards a standard patch

For your client portfolio

Agency portfolio review

€1,490 / one-time

One view of the PHP environments you look after.

Discuss your portfolio
  • Up to 20 sites across 5 servers or accounts
  • Runtime inventory and risk priorities
  • Client-ready, agency-branded report
  • Remediation quoted separately

Prices exclude applicable taxes. Standard remediation covers one supported server and one application, subject to assessment. Major upgrades and incident investigation are quoted separately.

Full service scope

A technical partner
behind your agency.

When every client asks the same question, you need a coordinated response. Get a portfolio inventory, a prioritised plan, and reports ready to share under your name.

Let’s review your portfolio Start with one agreed pilot. Expand with confidence.
Portfolio overviewExample
Commerce platformVendor patch confirmed
Verified
Client portalUpdate window to agree
Action needed
Legacy applicationCompatibility review first
Review
A clear status for every scoped environment.

Good questions.
Straight answers.

Understand the scope
before you commit.

Does updating WordPress fix PHP2Shell?

Not on its own. These vulnerabilities affect the PHP runtime beneath your application. WordPress, plugin and theme updates do not replace the required PHP security update.

My host says I’m protected. Do I still need this?

Your hosting provider may already have handled it. Ask for confirmation covering your actual PHP runtime and package. If you have that evidence, you may not need our service. Verification is useful when the status is unclear or you need a documented view across several environments.

Is Cloudflare enough?

Cloudflare has deployed WAF mitigations, but also recommends patching PHP. A firewall is an additional layer of protection, not evidence that your PHP runtime has been updated.

What if my application uses an older PHP version?

We check whether a supported vendor security backport is available. If a larger upgrade or application change is needed, we scope it separately. Major PHP migrations, operating-system upgrades and application rewrites are not included in the standard patch package.

How soon can work start?

We confirm availability after reviewing your environment. The agreed work window depends on scope, access and backup readiness. We do not make changes before the scope and maintenance window are approved.

Does the report prove that we were never compromised?

No. Verification documents the patch status and agreed functional checks. A previous compromise requires a separate investigation. If we see signs that warrant investigation, we flag them and discuss the next steps.

Let’s take care of your PHP.

Tell us what you run. We’ll agree the next step.

Get an assessment

Technical guidance reviewed 22 October 2026. Refer to the PHP advisory for the latest information. Managed hosting may already include the required update.