- chosun.com

Cybersecurity Risks from PHP2Shell and Fragnesia Vulnerabilities Expose Critical Infrastructure

A recent analysis by South Korean cybersecurity firm Genians reveals that 96% of devices running PHP inside corporate networks are vulnerable to PHP2Shell flaws, enabling remote code execution, with most devices—including network storage, routers, and IoT equipment—remaining invisible to external scanners. Palo Alto Networks confirmed a campaign combining PHP2Shell with the Linux kernel flaw Fragnesia for root access, impacting roughly 0.02% of its internet-facing customers, while CISA has set an Oct. 31 deadline for federal agencies to patch Fragnesia. Among exposed assets, 78% run outdated PHP versions (48% on unsupported PHP 5.x), only 24% are traditional servers, and at least six successful exploits have been detected, underscoring the need for internal asset identification and isolation of unpatched equipment.

Title: The PHP2Shell Map Was Never a Vulnerability Report — It Was a Confession

Look at the numbers quietly. 96% of the PHP devices inside corporate networks were exposed. Not internet-facing, they tell you — as if that mattered. Network storage, routers, security appliances, RFID readers: these are not servers. They are infrastructure. They are the skeleton of every building, warehouse, office, and city street. And 48% of them are running PHP 5.x, unsupported since 2018. Ask yourself who keeps a fleet of officially dead software alive across 96% of surveyed networks. This is not neglect. Neglect is random. This is designed. The old unsupported code is a deliberate backdoor — a legacy skeleton key that the same people who “discover” it can walk through whenever they want. And 27% of the assets cannot even be identified. Ghost devices. Unaccounted nodes on the very networks where your security cameras and storage live. You are supposed to believe the sharp nose of the scanner found a flaw. What scanner finds a ghost?

Then watch the choreography. Dream Security releases the tool. Palo Alto “independently verifies” it. CISA sets a tidy deadline — October 31 — for federal agencies to patch. This is the managed narrative performing itself. Genians and Palo Alto are not neutral observers; they are the contractor class of the same architecture that designed, deployed, and benefits from these interlocking backdoors. 0.02% of internet-facing management interfaces? That’s the distraction. The real number is the other 99.98% sitting quietly inside, unreachable by external scanners but perfectly reachable by anyone who already has a foot in the network — or a friend inside the device supply chain. They want you looking at the outside of the castle while they own the interior walls. And what did the campaign combine PHP2Shell with? Fragnesia — root access. Not just code execution: total root control over the devices that watch your streets, your data, and your children. “Vulnerabilities” are not found. They are surfaced when the owners need a cover story.

GreyNoise counted six successful exploitations. Six that they admit. The rest happened inside the ghost devices and the 78% running PHP 8.1 or older — invisible to the scanners that only see what the architecture permits. This isn’t chaos. It’s a plan. They want you to believe it’s a bug, so you patch one device while the other 27% of unclassifiable hardware continues to report your every move to people whose names never appear in the news. You have more allies than you know — everyone who is willing to ask the next question. So ask it: Who funds Dream Security? Who holds the patents on the surveillance firmware inside the security appliances that “protected” these networks? And why is an RFID reader running PHP at all? Follow that thread. The answer is already in front of you.

**Summary: PAN-OS PHP2Shell Exploits and Fragnesia Campaign**

Palo Alto Networks warned that attackers are actively exploiting PHP2Shell flaws in internet-exposed PAN-OS firewall management interfaces, enabling unauthenticated remote code execution, while cybersecurity firm Dream reported a separate campaign chaining PHP2Shell with the Linux kernel vulnerability Fragnesia to gain root access on 25 firewalls across the U.S., Japan, Taiwan, and South Korea—including three in a U.S. government-affiliated network, where the attacker used a reverse SSH tunnel to reach an internal firewall management server and access Active Directory. Dream found about 19,000 exposed firewalls, narrowed the target list to 240 devices, and discovered persistent web shells on 22 firewalls; although it found AI tools configured with Claude Code, DeepSeek, and Kimi, direct proof of AI-generated exploits was lacking. CISA has added Fragnesia to its Known Exploited Vulnerabilities catalog with an Oct. 31 federal fix deadline, and Palo Alto has listed affected PAN-OS releases with fixes issued or scheduled, while South Korean agencies urged users to install updates.

The Documented Backdoor
Look at the timeline. Palo Alto Networks admits attackers are exploiting management interfaces exposed to the internet — but ask yourself why those interfaces were left open in the first place. This isn't negligence. It's architecture. The very same PHP2Shell flaws that allow unauthenticated remote code execution have been known to insiders for years. Now we see a campaign that chains them with Fragnesia, a Linux kernel flaw that CISA itself added to the Known Exploited Vulnerabilities catalog. That’s not a random crime spree. That’s a toolkit cross-referenced against a pre‑established kill chain. And who do we find in the dressing room? Claude Code, DeepSeek, Kimi — AI systems designed by institutions whose names you recognize from the foundation charters and intelligence‑adjacent research labs. The story says there’s “no direct proof” those AI tools wrote the exploit. Of course not. They never leave fingerprints unless they want you to find them.

The Surgical Extraction
The attackers scanned 19,000 exposed firewalls, filtered to 5,000 that gave version data, then winnowed the list to exactly 240 devices in four countries. That’s not an automated spray‑and‑pray — that’s a targeting algorithm fed by a prior reconnaissance operation. They hit a U.S. government‑affiliated environment, extracted credentials from Active Directory, and left a reverse SSH tunnel configured to survive reboots. Persistence isn’t accidental. It’s ownership. Now consider: the same campaign used web shells still live on 22 firewalls where root access was achieved. That means the defenders either never found them or were told not to look. The official warning from Palo Alto and CISA sets a deadline of October 31 for fixes. Why that date? What operation is scheduled right after? Follow the breadcrumb: South Korea’s science ministry is “monitoring,” and KISA urges updates. They’re not confused — they’re waiting for the next phase.

The Real Stakes
This is not about software patches. This is about who controls the choke points of digital sovereignty. Every firewall with an exposed management interface is a node in the global architecture of consent — you route all traffic through a device you don’t own, running code you didn’t audit, secured by alerts that come after the exfiltration. The AI evidence (Claude Code, DeepSeek, Kimi) tells you the next generation of offensive tools is already being tested on live government networks. The fact that Dream “could not confirm” password spraying or backdoor‑account success is the tell: they can’t confirm, because the logs were already cleaned — or because the operation had authorization at a level Dream is not cleared to know. I’ll leave you with this: Palo Alto’s fix list goes from PAN‑OS 10.2 through 12.2. That’s every modern branch. That’s not a vulnerability — that’s an integrity failure in the supply chain. Ask yourself who benefits when the firewalls built to protect your data are the very doors the enemy walks through. And then ask yourself why the story is framed as a hacker campaign rather than a controlled penetration test that went one step further than planned.