PHP2Shell Is Already Exploited. Patch the Gear, and Fund CISA and NIST.
Crazy week for tech failures, right? This one has two halves. The first half is PHP, the language running behind a huge number of websites and, it turns out, a fair amount of office gear. The second half is whether the agencies that coordinate a response like this have the people and money to do it.
If you run an MSP, the first half is your week. The second half is your future workload. Let's take them in that order.
You can watch the short version here:
The video uses a digital avatar of Erick Grau, CEO of Chibitek.
What Is PHP2Shell?

PHP2Shell: unauthenticated remote code execution in the PHP engine. Sources: PHP project advisory, Oct. 21, 2026; CISA alert, updated Oct. 26, 2026.
PHP2Shell is the name for two critical bugs in PHP itself, CVE-2026-109618 and CVE-2026-109619. On Oct. 21, 2026, the PHP project released fixes and said the two bugs "can allow unauthenticated remote code execution." Both are rated CVSS v4.0 9.2 by PHP. In plain words, someone who can reach a PHP web server may be able to run their own code on it without logging in.
PHP says every installation that serves web requests is at risk, including PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP, and LiteSpeed. It considers mod_php the highest risk. It also says there are no complete mitigations, and that updating is the way to fix it.
On Oct. 26, CISA added both CVEs to its Known Exploited Vulnerabilities (KEV) catalog. That catalog is CISA's list of vulnerabilities that have been exploited in the wild. So this is not a theoretical bug. It is being used.
What Should MSPs Patch First?

CISA says to update immediately to PHP 8.5.12, 8.4.27, 8.3.36, or 8.2.35. Sources: CISA PHP2Shell alert; CISA KEV guidance.
The fixed versions are PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35. CISA's alert lays out the order of work, and it maps well to how an MSP runs a patch week:
Inventory every system running PHP. CISA warns that "PHP is often a component of other software and prevalence may not be directly observable." That includes appliances and management tools, not just the web servers you know about.
Patch internet-facing systems first. CISA says to apply the patch immediately, prioritizing internet-facing systems.
Take it offline if you cannot patch. CISA says organizations that cannot update right away, or that still run PHP 8.1 or earlier, should take PHP-based systems offline until they are patched or updated.
Treat a web application firewall as a stopgap. CISA says a WAF "may provide some protection" until systems are updated. It is not the fix.
Watch for signs of compromise. CISA says to monitor for PHP worker processes launching shells or downloading tools.
Linux distributions and long-term support vendors received the patches in advance, according to PHP, so check your distribution's packages as well as php.net.
Is This Only About Websites?

Vendor status as of each vendor's own PHP2Shell advisory, checked Nov. 15, 2026. Read the advisory for your exact model.
No. PHP shows up inside routers, printers, and management software, usually behind the little web page you use to configure the device. Here is what the vendors themselves say:
NETGEAR lists Nighthawk models including the RAX28 and CAX30. It says PHP is used only for local web management, is "not accessible from the Internet by default," and rates the issue Medium. Fixed firmware is pending. Until then, NETGEAR advises not letting untrusted users onto your Wi-Fi.
Xerox lists specific printer lines. Some AltaLink and VersaLink models are already remediated with PHP 8.2.35; others, such as WorkCentre 3655 and Fiery front ends, have a patch or a scheduled patch window. Xerox says the vulnerable component is used by a limited number of Embedded Web Server pages and recommends restricting network access to the device until it is patched.
Kyocera lists KYOCERA Net Manager / aQrate and several Printing System versions as affected, with a fix for Net Manager / aQrate 10.2 (Patch 29).
HP lists its consumer, enterprise, DesignJet, and PageWide XL printers as not affected. HP Device Manager versions before 5.0.18 are affected; HP has released a mitigation patch, and the fix ships in 5.0.18.
D-Link says its currently marketed routers, switches, wireless access points, and network cameras do not use PHP and are not affected.
Lexmark says its product security team is still reviewing Lexmark and Xerox products.
Notice the pattern. Each vendor's answer is model by model. A brand that is not on an advisory, or a model that is not listed yet, is not the same as a model that has been cleared.
What About the Forgotten Gear?
When was the last time you logged into the office Wi-Fi router? Or the printer's admin page? This is where a bug like PHP2Shell lives longest.
Both Xerox and Kyocera recommend the same interim step: keep the device's web interface off the public internet and restrict who can reach it until it is patched. Our own checklist for clients and our own shop adds two habits:
Read the vendor advisory for the exact model, and set a reminder to check back, because several of these are still being updated.
Change default admin passwords on routers and printers, and do not leave their admin pages reachable from the internet.
Who Coordinates a Response Like This?

CISA enacted budget, FY2025 and FY2026, and the workforce reduction. Sources: CRS R48115; Public Law 119-86; CBS News and Federal News Network on staffing.
Here is the other half. Small businesses and MSPs do not have time to research every CVE from scratch. We rely on public infrastructure to tell us what matters:
CISA's KEV catalog tells you what is being exploited. CISA "strongly recommends all organizations review and monitor the KEV catalog and prioritize remediation," and federal civilian agencies are required to remediate KEV entries on set timelines.
NIST's National Vulnerability Database adds the details teams use to act on a CVE.
CISA's emergency directives set the pace in a national event. For SolarWinds, Emergency Directive 21-01 told federal civilian agencies to disconnect or power down affected SolarWinds Orion products. For Log4j, Emergency Directive 22-02 required agencies to patch internet-facing systems, and pointed to a CISA-managed public GitHub list of affected products. CISA also published Log4j guidance with industry members of its Joint Cyber Defense Collaborative.
That capacity still exists. CISA is the agency that put PHP2Shell on the KEV list. But it is thinner than it was:
CISA's budget is lower. CISA's enacted funding was $2,873,008,000 for fiscal 2025. For fiscal 2026, Public Law 119-86 provides $2,218,634,000 for operations and support plus $386,464,000 for procurement, construction, and improvements, a total of $2,605,098,000. That is a reduction of about $268 million.
CISA's workforce is smaller. CBS News reported that nearly 1,000 CISA personnel, nearly one-third of the workforce, had left or been removed from active service by mid-2025. Federal News Network has also reported CISA losing roughly one-third of its staff.
The NVD is triaging. In April 2026, NIST said it had been unable to clear a backlog of unenriched CVEs that began in early 2024. Starting April 15, 2026, it prioritizes CVEs in CISA's KEV catalog, federal software, and critical software, and moved backlogged CVEs published before March 1, 2026 to "Not Scheduled." The Commerce Department's Inspector General reported the backlog grew from about 13,000 in June 2024 to over 27,000 by the end of 2025.
The information-sharing law is on a short leash. The Cybersecurity Information Sharing Act of 2015, which gives companies legal protections when they share cyber threat information, is currently effective only through December 11, 2026, under a series of short-term extensions.
This is not about one party or one person. Funding for these agencies is a choice Congress makes every year, and it is a choice that lands on every MSP and small business when the next bug drops.
What Can You Do About the Funding?
Tell your elected officials what you see in the field. The official lookup is usa.gov/elected-officials. A short, specific message works best:
Fund CISA and NIST so they can keep the KEV catalog, the National Vulnerability Database, and national incident coordination running.
Give the 2015 cybersecurity information-sharing law a real reauthorization, not another short-term extension.
Tell them who you are: an MSP, a small business owner, or an IT lead who depends on that work every patch week.
Key Points of PHP2Shell
PHP2Shell is two critical bugs in PHP, CVE-2026-109618 and CVE-2026-109619, that can allow unauthenticated remote code execution.
PHP patched them on Oct. 21, 2026. CISA added both to its KEV catalog on Oct. 26. Update to 8.5.12, 8.4.27, 8.3.36, or 8.2.35.
Inventory every system running PHP, including inside other software. Patch internet-facing systems first, and take systems offline if you cannot patch.
Routers, printers, and management tools can ship PHP. Read the vendor advisory for the exact model.
CISA's enacted budget fell about $268 million from fiscal 2025 to fiscal 2026, and its workforce fell by roughly a third. NIST is triaging NVD enrichment.
Contact your elected officials at usa.gov/elected-officials and ask them to fund CISA and NIST and reauthorize the 2015 information-sharing law.
Frequently Asked Questions
Which PHP versions fix PHP2Shell? PHP 8.5.12, 8.4.27, 8.3.36, and 8.2.35, according to the PHP project and CISA.
What if a system runs PHP 8.1 or earlier? CISA says organizations that cannot update right away, or that still run PHP 8.1 or earlier unsupported versions, should take PHP-based systems offline until they can be patched or updated.
Is a web application firewall enough? No. CISA says a WAF may provide some protection until systems are patched. PHP says there are no complete mitigations.
Are my routers and printers affected? It depends on the exact model. NETGEAR, Xerox, Kyocera, and HP have named specific affected products, D-Link says its current hardware is not affected, and Lexmark is still reviewing. Check each vendor's own advisory.
Why does CISA funding matter to an MSP? CISA's KEV catalog is one of the clearest public signals of what to patch first, and NIST's NVD supplies the details behind each CVE. When those agencies are thinner, more of that research lands on your team.
Let's Patch Smarter Together
At Chibitek, we are an MSP talking to MSPs and the businesses we serve. Patch the gear you know about, find the gear you forgot, and make your voice heard on the public infrastructure we all depend on. If you want a second set of eyes on your PHP2Shell inventory, contact us at hello@chibitek.com.
You can watch the short version here:
The same video is also on LinkedIn.
We make IT effortless so you can create, disrupt, and grow!
Follow Chibitek on YouTube at @chibitekmsp, and follow Chibitek on LinkedIn.
Sources
PHP project. Security advisory, "Critical remote code execution vulnerabilities, update now," Oct. 21, 2026. https://www.php.net/archive/2026.php
PHP project. GitHub security advisories GHSA-w8hw-w9fx-j79w and GHSA-6wmf-4rv5-p3rp. https://github.com/php/php-src/security/advisories/GHSA-w8hw-w9fx-j79w and https://github.com/php/php-src/security/advisories/GHSA-6wmf-4rv5-p3rp
CISA. "Critical Vulnerabilities in PHP Require Immediate Patching," last revised Oct. 26, 2026. https://www.cisa.gov/news-events/alerts/2026/10/21/critical-vulnerabilities-php-require-immediate-patching
CISA. Known Exploited Vulnerabilities catalog. https://www.cisa.gov/known-exploited-vulnerabilities-catalog
CISA. "Reducing the Significant Risk of Known Exploited Vulnerabilities." https://www.cisa.gov/known-exploited-vulnerabilities-catalog/reducing-significant-risk-known-exploited-vulnerabilities
NETGEAR. Security Advisory for PHP2Shell Vulnerabilities (article 000070960). https://kb.netgear.com/000070960/NETGEAR-Security-Advisory-for-PHP2Shell-Vulnerabilities
Xerox. Security Bulletin XRX26-016, updated Nov. 6, 2026. https://securitydocs.business.xerox.com/wp-content/uploads/2026/11/Xerox-Security-Bulletin-XRX26-016-for-PHP2Shell-Vulnerabilities-CVE-2026-109618-and-CVE-2026-109619-v6.pdf
Kyocera Document Solutions. Security information, Oct. 22, 2026. https://www.kyoceradocumentsolutions.com/global/en/support-and-download/security-information/info_20261022.html
HP. "PHP Vulnerabilities also known as PHP2Shell." https://support.hp.com/us-en/document/ish_15892944-15892989-16
HP. HP Device Manager Security Update, HPSBHF04160. https://support.hp.com/us-en/document/ish_15893017-15893060-16
D-Link. Security announcement SAP10524, Nov. 10, 2026. https://supportannouncement.us.dlink.com/security/publication.aspx?name=SAP10524
Lexmark. Current security advisories. https://www.lexmark.com/en_us/solutions/security/lexmark-security-advisories/current-advisories.html
CISA. Emergency Directive 21-01, SolarWinds Orion. https://www.cisa.gov/news-events/directives/ed-21-01-mitigate-solarwinds-orion-code-compromise-closed
CISA. Emergency Directive 22-02, Apache Log4j. https://www.cisa.gov/news-events/directives/ed-22-02-mitigate-apache-log4j-vulnerability-closed
CISA, FBI, NSA and international partners. AA21-356A, "Mitigating Log4Shell and Other Log4j-Related Vulnerabilities." https://www.cisa.gov/news-events/cybersecurity-advisories/aa21-356a
Congressional Research Service. R48115, DHS appropriations tables. https://www.congress.gov/crs_external_products/R/HTML/R48115.html
DHS. CISA budget overview (FY2027 request, with FY2025 enacted). https://www.dhs.gov/sites/default/files/2026-04/26_0403_ocfo-budget-cisa.pdf
Public Law 119-86, Department of Homeland Security appropriations for fiscal 2026. https://www.congress.gov/119/plaws/publ86/PLAW-119publ86.htm
CBS News. CISA workforce reductions. https://www.cbsnews.com/news/trump-election-security-cisa-justice-department-fbi-federal-worker-cuts/
Federal News Network. "Three highlights in latest DHS spending bill," June 2026. https://federalnewsnetwork.com/budget/2026/06/three-highlights-in-latest-dhs-spending-bill/
NIST. "NIST Updates NVD Operations to Address Record CVE Growth," April 15, 2026. https://www.nist.gov/news-events/news/2026/04/nist-updates-nvd-operations-address-record-cve-growth
U.S. Department of Commerce, Office of Inspector General. Evaluation of NIST's Management of the National Vulnerability Database (OIG-26-020-I). https://www.oversight.gov/sites/default/files/documents/reports/2026-05/OIG-26-020-I%20%28SECURED%29.pdf
6 U.S.C. 1510, effective period of the Cybersecurity Information Sharing Act of 2015. https://uscode.house.gov/us/usc/t6/s1510/
Congressional Research Service. IF12959, "The Cybersecurity Information Sharing Act of 2015: Expiring Provisions." https://www.congress.gov/crs-product/IF12959
USAGov. Find and contact elected officials. https://www.usa.gov/elected-officials








Comments