By DESSS · Published November 18, 2026 · Last updated November 18, 2026 · 7 min read

PHP2Shell is one exploit, but finding out whether it worked takes scan, network and endpoint evidence together.
Quick answer: PHP2Shell is a pair of critical PHP engine flaws (CVE-2026-109618 and CVE-2026-109619) that can let attackers run code on unpatched servers without logging in. Upgrade to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, then check scan, IDS, network and endpoint data together to confirm whether any attack attempt succeeded.
On this page
PHP2Shell is the name for two memory-safety bugs in the PHP engine. Both are rated critical and can lead to remote code execution, meaning an outsider can run commands on your server. The flaws sit in how PHP processes a request before your application code runs, so your own login and input checks may never get the chance to stop it.
Need help upgrading safely? Our guides cover PHP upgrades on Linux servers, PHP upgrades on Windows Server with IIS and Apache, and how PHP upgrades affect MySQL, SQL Server, Oracle and PostgreSQL connections.
Severity
CVSS 9.8 · Critical
Login needed
None (unauthenticated)
Impact
Remote code execution
Fixed in
PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35
CVE-2026-109618 is one of the two PHP2Shell vulnerabilities in core PHP. It is a memory-safety flaw in the PHP engine, rated CVSS 9.8 (critical), that can let an attacker run code on an unpatched server without logging in. Because it sits in the runtime rather than in your application, your own login and input checks may never get the chance to stop it.
Is your site exposed? Any server running a PHP release older than the fixed versions above is at risk, especially internet-facing setups such as PHP-FPM, Apache with mod_php, php-cgi, FrankenPHP and LiteSpeed. A PHP2Shell vulnerability scan shows which of your servers need the patch first.
Severity
CVSS 9.8 · Critical
Login needed
None (unauthenticated)
Impact
Remote code execution
Fixed in
PHP 8.5.12, 8.4.27, 8.3.36, 8.2.35
CVE-2026-109619 is the second PHP2Shell vulnerability. It is also a critical memory-safety flaw in the PHP engine, rated CVSS 9.8, and it was fixed in the same PHP releases on October 21, 2026. Patching only part of your estate leaves the door open, so treat both CVEs as one upgrade.
PHP2Shell attacks arrive as multipart POST requests that use PHP's session upload-progress feature. If you can't upgrade today, the temporary measures below reduce risk until the patch is in place, and managed patching keeps the next critical PHP fix from waiting in a queue.
PHP2Shell deserves urgent attention, but patching it is only half the lesson. The flaw shows that most security teams see attacks through a keyhole: each tool watches one slice, and nobody sees the full room.
When a serious vulnerability lands, four questions come fast. Which of our systems are exposed? Has anyone tried to exploit them? Did any attempt succeed? What did the attacker do next? Answering all four takes evidence from many places, and that evidence rarely lives in one console.
Think of an attack as a story told in chapters, with each chapter recorded by a different witness.
Each witness is useful. The trouble starts when they never compare notes. An analyst who sees only an IDS alert may dismiss it as noise. One who sees only a scan result may queue the patch for next month. Meanwhile, the endpoint quietly logs a web shell nobody connects to either event.
List every server running PHP and compare its version with the fixed releases. Start with internet-facing systems, servers that hold sensitive data and machines linked to critical infrastructure. Those get patched or shielded first.
Link the scanner finding for each host to the IDS alerts aimed at it, the network flows around it and the endpoint activity on it. One timeline per asset beats a dozen tickets spread across a dozen tools.
Exploit traffic is common; successful compromise is what matters. Look for these warning signs on targeted hosts:
Once a compromise is confirmed, act across layers at once: isolate the endpoint, block attacker addresses at the firewall, reset exposed credentials, remove the web shell and patch the remaining hosts. Coordinated action closes the gaps that one-tool fixes leave open.
Temporary measures only. These reduce risk while you schedule the upgrade; they don't replace it.
PHP_SESSION_UPLOAD_PROGRESS.PHP2Shell shows how short the window has become. F5 Labs saw scanning begin more than five hours before the CVEs and patches were even published, and recorded thousands of exploit attempts within hours of disclosure.
That leaves no room for a process where data is exported from one tool, pasted into another and discussed over email before anyone acts. What works is an operating model built on connection, not collection. Signals from scanners, sensors, endpoints, identity systems and cloud platforms should flow into a shared view. There they can be correlated automatically, ranked by business risk and handed to responders with context attached. The goal isn't more alerts. It's fewer, better ones that each tell a complete story.
Patch PHP2Shell now, but fix the visibility gap too. The next flaw is already on its way. Teams that see exposure, exploitation and impact side by side answer the critical questions in minutes instead of days.
Many Houston and Austin companies run PHP behind their websites, customer portals and internal tools, often on servers nobody has reviewed in years. DESSS's Houston and Austin teams can find every PHP server you run, patch PHP safely, check for signs of compromise and set up monitoring so the next critical flaw doesn't catch you off guard. That includes healthcare, legal, engineering and enterprise sites across Texas.
We do services across the globe, including the cities below. DESSS runs PHP2Shell vulnerability scans, patches PHP safely and checks servers for signs of compromise wherever your sites are hosted.
Texas TX
Austin · Houston · San Antonio · Dallas · Fort Worth · El Paso · Arlington · Corpus Christi · Plano · Lubbock
Alabama AL
Montgomery · Huntsville · Birmingham · Mobile · Tuscaloosa · Hoover
Alaska AK
Juneau · Anchorage · Fairbanks · Sitka · Ketchikan · Wasilla
Arizona AZ
Phoenix · Tucson · Mesa · Chandler · Scottsdale · Glendale · Tempe · Flagstaff
Arkansas AR
Little Rock · Fayetteville · Fort Smith · Springdale · Jonesboro · Rogers
California CA
Sacramento · Los Angeles · San Diego · San Jose · San Francisco · Fresno · Long Beach · Oakland · Bakersfield · Anaheim
Colorado CO
Denver · Colorado Springs · Aurora · Fort Collins · Lakewood · Boulder · Pueblo
Connecticut CT
Hartford · Bridgeport · New Haven · Stamford · Waterbury · Norwalk
Delaware DE
Dover · Wilmington · Newark · Middletown · Smyrna
Florida FL
Tallahassee · Jacksonville · Miami · Tampa · Orlando · St. Petersburg · Fort Lauderdale · Hialeah
Georgia GA
Atlanta · Augusta · Columbus · Savannah · Athens · Macon
Hawaii HI
Honolulu · Hilo · Kailua · Pearl City · Kahului
Idaho ID
Boise · Meridian · Nampa · Idaho Falls · Pocatello · Coeur d’Alene
Illinois IL
Springfield · Chicago · Aurora · Naperville · Joliet · Rockford · Peoria
Indiana IN
Indianapolis · Fort Wayne · Evansville · South Bend · Carmel · Bloomington
Iowa IA
Des Moines · Cedar Rapids · Davenport · Sioux City · Iowa City · Waterloo
Kansas KS
Topeka · Wichita · Overland Park · Kansas City · Olathe · Lawrence
Kentucky KY
Frankfort · Louisville · Lexington · Bowling Green · Owensboro · Covington
Louisiana LA
Baton Rouge · New Orleans · Shreveport · Lafayette · Lake Charles · Monroe
Maine ME
Augusta · Portland · Lewiston · Bangor · South Portland · Auburn
Maryland MD
Annapolis · Baltimore · Frederick · Rockville · Gaithersburg · Hagerstown
Massachusetts MA
Boston · Worcester · Springfield · Cambridge · Lowell · Brockton
Michigan MI
Lansing · Detroit · Grand Rapids · Warren · Sterling Heights · Ann Arbor · Flint
Minnesota MN
St. Paul · Minneapolis · Rochester · Duluth · Bloomington · Brooklyn Park
Mississippi MS
Jackson · Gulfport · Southaven · Hattiesburg · Biloxi · Tupelo
Missouri MO
Jefferson City · Kansas City · St. Louis · Springfield · Columbia · Independence
Montana MT
Helena · Billings · Missoula · Great Falls · Bozeman · Butte
Nebraska NE
Lincoln · Omaha · Bellevue · Grand Island · Kearney
Nevada NV
Carson City · Las Vegas · Henderson · Reno · North Las Vegas · Sparks
New Hampshire NH
Concord · Manchester · Nashua · Dover · Rochester · Portsmouth
New Jersey NJ
Trenton · Newark · Jersey City · Paterson · Elizabeth · Camden · Atlantic City
New Mexico NM
Santa Fe · Albuquerque · Las Cruces · Rio Rancho · Roswell
New York NY
Albany · New York City · Buffalo · Rochester · Yonkers · Syracuse
North Carolina NC
Raleigh · Charlotte · Greensboro · Durham · Winston-Salem · Fayetteville · Wilmington · Asheville
North Dakota ND
Bismarck · Fargo · Grand Forks · Minot · West Fargo
Ohio OH
Columbus · Cleveland · Cincinnati · Toledo · Akron · Dayton
Oklahoma OK
Oklahoma City · Tulsa · Norman · Broken Arrow · Edmond · Lawton
Oregon OR
Salem · Portland · Eugene · Gresham · Hillsboro · Bend · Medford
Pennsylvania PA
Harrisburg · Philadelphia · Pittsburgh · Allentown · Erie · Reading · Scranton
Rhode Island RI
Providence · Warwick · Cranston · Pawtucket · Newport
South Carolina SC
Columbia · Charleston · North Charleston · Greenville · Rock Hill · Myrtle Beach
South Dakota SD
Pierre · Sioux Falls · Rapid City · Aberdeen · Brookings
Tennessee TN
Nashville · Memphis · Knoxville · Chattanooga · Clarksville · Murfreesboro
Utah UT
Salt Lake City · West Valley City · Provo · West Jordan · Orem · Ogden · St. George
Vermont VT
Montpelier · Burlington · South Burlington · Rutland · Barre
Virginia VA
Richmond · Virginia Beach · Norfolk · Chesapeake · Arlington · Newport News · Alexandria
Washington WA
Olympia · Seattle · Spokane · Tacoma · Vancouver · Bellevue · Everett
West Virginia WV
Charleston · Huntington · Morgantown · Parkersburg · Wheeling
Wisconsin WI
Madison · Milwaukee · Green Bay · Kenosha · Racine · Appleton
Wyoming WY
Cheyenne · Casper · Laramie · Gillette · Rock Springs
Request a PHP2Shell vulnerability scan →
PHP2Shell is the name for two critical memory-safety flaws in the PHP engine, CVE-2026-109618 and CVE-2026-109619. Both are rated CVSS 9.8 and can let an unauthenticated attacker run code on an unpatched server. PHP released fixes on October 21, 2026.
According to F5 Labs, the fixed releases are PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35. Servers on older releases of those branches, or on unsupported PHP versions, should be upgraded or isolated as soon as possible.
Any site running an unpatched PHP engine that handles web requests may be at risk, including common setups such as PHP-FPM and Apache with mod_php. The flaw sits in the runtime, so it can be reached before your application's own login or input checks run.
A scanner shows which servers are exposed, but not whether anyone exploited them. IDS and network data show attack attempts, and endpoint and identity data show what happened afterward. You need all three to know if you were breached.
Check the targeted host for new PHP files in web directories, shell or system commands spawned by the web server process, outbound connections to unknown addresses, and unexpected logins or credential use after the attack time.
Reduce exposure while you schedule the upgrade: disable the session upload-progress feature, use a web application firewall or virtual patch to drop requests carrying PHP_SESSION_UPLOAD_PROGRESS, and watch closely for scanning and unusual upload activity.
DESSS helps Houston and Austin businesses upgrade PHP safely, check servers for signs of compromise and connect their security tools into one response plan.
Talk to a Houston or Austin PHP security expert →
DESSS · 2825 Wilcrest Dr #608, Houston, TX 77042 · (713) 589-6496 · info@desss.com
Disclaimer: This article is for general information only and is not professional security, legal or compliance advice. Threat details, affected versions and recommended fixes can change quickly, so always check official PHP and vendor advisories before acting. Any steps you take based on this content are at your own discretion and risk. Mentions of tools or approaches are illustrative and do not endorse any specific product or vendor.