CISA
US Cybersecurity and Infrastructure Security Agency ·
Read the official advisory →“CISA strongly urges organizations to immediately patch the recently disclosed critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619.”
A critical PHP flaw, disclosed Oct 21, 2026. Find out in a free 30-second check — no login needed.
Official warnings · CVE-2026-109618 & CVE-2026-109619
Government security agencies, the PHP project and major cloud providers all rate this flaw as critical. Short quotes, word for word, with screenshots of each page.
US Cybersecurity and Infrastructure Security Agency ·
Read the official advisory →“CISA strongly urges organizations to immediately patch the recently disclosed critical vulnerabilities in PHP, CVE-2026-109618 and CVE-2026-109619.”
Cybersecurity Service for the EU institutions ·
“Both vulnerabilities can allow unauthenticated remote code execution.”
Read the official advisory →“CERT-EU advises organisations to patch affected assets immediately.”
Government of Canada ·
“Internet-facing PHP servers and applications are at heightened risk.”
Read the official advisory →“Organizations should identify affected systems and apply the appropriate updates immediately.”
Official php.net security advisory ·
“PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35 fix two critical vulnerabilities that can allow unauthenticated remote code execution.”
Read the official advisory →“All PHP users are strongly encouraged to update immediately.”
CVE-2026-109618 · CVSS 9.2 Critical ·
Read the official advisory →“Multiple OOM strategies can consistently trigger this condition and lead to remote code execution (RCE).”
Google Cloud security blog ·
Read the official advisory →“The PHP project is not releasing fixes for PHP 8.1 or earlier, which have reached end of life.”
AWS security bulletin ·
Read the official advisory →“Two critical issues have been identified in PHP web runtimes (CVE-2026-109618 and CVE-2026-109619) that can allow an unauthenticated actor to run code on affected systems.”
Independent sources — we are not affiliated with these organisations. Screenshots captured Oct 24, 2026; the official pages may since have been updated.
CISA had not observed successful exploitation as of its alert, but urges patching now. Sources above.
Your store or site runs on an engine called PHP — WooCommerce, Magento, PrestaShop, OpenCart, custom PHP and more. Your version decides the fix.
PHP 8.1 or older. No simple patch — Safe PHP Upgrade: free review, fixed price.
PHP 8.2–8.5 below those numbers. Patch & Verify: $100 per store.
PHP 8.2.35, 8.3.36, 8.4.27, 8.5.12 or newer. Nothing to do.
One flat price for the patch, held in secure escrow until you’re happy. We confirm which option fits before you pay anything.
From $100 Per website · Scope confirmed first
Review your PHP setup with our team, then agree the patching work your website needs.
Free consultation · No payment to book.
From $100 Per website · Scope confirmed first
Prefer Upwork? Discuss your website with HestaBit and agree the project through our profile.
Project price and platform fees confirmed on Upwork
Custom quote Per website
Older PHP versions need a closer review. We assess compatibility and plan the right upgrade.
Free consultation · Upgrade quoted separately
Patching eligibility depends on your hosting and application. Major upgrades and extensive code changes are quoted separately.
The same five steps for every job, so you always know who has access and what we touch.
We confirm your PHP version and send a short written plan. You approve the scope and price, then pay into escrow — not to us.
You create a separate login just for us (hosting panel or SFTP) and can revoke it any time. We never ask for passwords by email. NDA on request.
We take a backup and, where needed, test on a staging copy on your own hosting. We only touch the PHP version, its settings and compatibility code — we don’t open, copy or export customer, order or payment data.
At a low-traffic time you choose. If anything looks wrong, we roll back to the backup.
We re-test key pages and checkout and send a before/after report. You confirm, revoke our access and release the escrow.
Delivered by HestaBit
HestaBit is a PHP and e-commerce engineering partner helping brands and store owners ship stable systems, faster upgrades, and safer production builds. The work spans PHP hardening, platform upgrades, performance tuning, and custom e-commerce delivery for live business-critical storefronts.
Only temporary, limited access for the job you approve — usually a separate hosting-panel or SFTP login that you create and can revoke any time. We never ask for passwords by email.
No. We only work on the PHP version, its settings and compatibility code. We don’t open, copy or export customer, order or payment data, and any staging copy stays on your own hosting. NDA on request.
Maybe not. On many managed hosts the fix is a PHP version switch in your hosting panel, or the host applies it for you. We’ll tell you which applies for free — or do it for you. If your host blocks the update and we can’t patch, the escrow refunds you in full.
You pay $100 into secure escrow when you book. You release it once you confirm your store is patched. If we can’t get your store onto the fixed PHP release — for example, your host blocks the update — the escrow refunds you in full. Stores on PHP 8.1 or older need a Safe PHP Upgrade instead; we quote that separately and you don’t pay the $100.
A patch within PHP 8.2–8.5 is usually low risk and needs no downtime, or a brief restart. Upgrades from older PHP are tested on a staging copy first and go live at a low-traffic time you choose, with a rollback plan.
No. It only reads public server headers that your site shows every visitor. Many hosts hide the PHP version — that’s normal, and we can check properly for free.
Two critical flaws in PHP itself (CVE-2026-109618 and CVE-2026-109619, CVSS 9.2), disclosed Oct 21, 2026. PHP is the engine behind WooCommerce, Magento, PrestaShop, OpenCart, custom PHP shops and many other websites. Official advisories are linked at the top of this page.
Enter the email address that received a StoreUpkeep message. We will stop sending marketing emails to it. Operational messages about a job you already booked may still be necessary.