Last updated: November 2, 2026 at 1:20 PM UTC
All 957 Vulnerability 399 Breach 144 Threat 407 Defense 7
Tag: php (5 articles)Clear

PHP ships emergency patches for two confirmed PHP2Shell code execution flaws as exploit attempts begin

PHP shipped emergency patches on October 21 for two runtime flaws collectively called PHP2Shell, now confirmed as CVE-2026-109618 and CVE-2026-109619 and rated 9.2, correcting the leaked 10.0 figure. They affect nearly every PHP version back to 5.4, with fixes in 8.5.12, 8.4.27, 8.3.36, and 8.2.35; branches 8.1 and older get no official update. Both live in the PHP runtime, so applications are exposed even with secure code, and the risk is highest under Apache mod_php. Cloudflare and watchTowr reported exploit attempts within hours, though no confirmed compromise. Wiz, Calif, and OpenAI's Codex Security team reported the flaws.

Check
Update PHP to 8.5.12, 8.4.27, 8.3.36, or 8.2.35 now, prioritizing Apache mod_php hosts, and migrate off end-of-life 8.1 and older.
Affected
Nearly every PHP version back to 5.4 carries two runtime flaws exposing applications to remote code execution and worker-memory reads regardless of the application's own code.
Fix
Install the PHP security releases, confirm distribution packages carry the CVE fixes, watch for exploit attempts now underway, and replace unsupported PHP branches.

PHP schedules emergency release for two critical remote code execution flaws after early details leak

A leaked post disclosed two critical PHP remote code execution flaws, dubbed PHP2Shell, prompting PHP to schedule an out-of-cycle security release at 14:00 UTC on October 21 for supported branches 8.2 through 8.5. PHP rated both flaws 9.2 and has not described the mechanism, affected versions, or feature requirements, which will come with the release; the leaked identifiers CVE-2026-109618 and CVE-2026-109619 are not confirmed by PHP. watchTowr verified the leak is real and that the flaws allow code execution. No exploitation was reported as of October 21, and end-of-life branches 8.1 and older will receive no fix.

Check
Prepare to apply PHP's out-of-cycle update for branches 8.2 through 8.5 as soon as it ships, and plan migration off end-of-life 8.1 and older.
Affected
Supported PHP branches 8.2 through 8.5 reportedly contain two critical remote code execution flaws, with end-of-life branches 8.1 and older receiving no fix at all.
Fix
Install the PHP security release immediately on all supported branches, upgrade off end-of-life versions, and watch for exploitation once the technical details become public.

WordPress SC backdoor rebuilds itself from files database and shared memory after cleanup

Sucuri detailed a WordPress compromise using a backdoor it codenamed SC, after SC_ markers in the injected content, which it describes as a self-healing mesh. The payload lives in at least eight places at once, spread across files, the database, and a shared-memory segment, and every location can rebuild all the others. Cleaning every file on disk lets the next page load restore the whole set from the database or shared memory, so there is no single point to remove. The malware carries no readable function names, using a substitution cipher to unscramble its code, and a .user.ini auto_prepend_file runs a loader before every PHP request.

Check
Treat infected WordPress sites as needing coordinated full cleanup across files, database, and runtime, and rebuild from a known-good backup where feasible.
Affected
WordPress sites hit by the SC backdoor cannot be cleaned piecemeal, since files, database entries, and shared memory each regenerate the removed components.
Fix
Take the site offline during cleanup, purge all eight component types together, rotate credentials and keys, restore from clean backups, and harden PHP auto_prepend_file.

Packagist supply-chain attack hits 8 Composer packages with cross-ecosystem package.json hook downloading Linux binary to /tmp/.sshd

Socket has detailed a coordinated supply-chain campaign that planted malicious code in eight Composer packages on Packagist, including moritz-sauer-13/silverstripe-cms-theme, crosiersource/crosierlib-base, devdojo/wave, devdojo/genesis, katanaui/katana, elitedevsquad/sidecar-laravel, r2luna/brain, and baskarcm/tzi-chat-ui. The attackers placed the payload not in composer.json but in package.json - meaning teams scanning only PHP dependencies would miss the Node.js lifecycle hook bundled inside. The postinstall script downloads a Linux binary from a GitHub Releases URL (github[.]com/parikhpreyash4/systemd-network-helper-aa5c751f), saves it as /tmp/.sshd, and runs it backgrounded with execute permissions. Socket found the same payload referenced in 777 GitHub files, including two GitHub Actions workflows - hinting at a broader campaign.

Check
Audit composer.lock and package.json across PHP projects for the 8 affected packages installed since 2026-05-20. Block egress to github[.]com/parikhpreyash4/* and check /tmp/.sshd presence on Linux build hosts.
Affected
Any project that installed moritz-sauer-13/silverstripe-cms-theme, crosiersource/crosierlib-base, devdojo/wave, devdojo/genesis, katanaui/katana, elitedevsquad/sidecar-laravel, r2luna/brain, or baskarcm/tzi-chat-ui via Composer. Hidden in package.json so PHP-only scanners miss it.
Fix
Roll affected packages back to clean versions; pin via composer.lock and package-lock.json. Rotate developer and CI credentials reachable from affected hosts. Scan PHP repos for package.json lifecycle hooks.

Laravel-Lang PHP packages compromised - autoload payload steals AWS, Azure, GCP, K8s, Vault, crypto wallets across Linux, macOS, Windows

Aikido Security and Socket have disclosed that several packages in the Laravel-Lang PHP ecosystem were compromised and used to ship a ~5,900-line PHP credential stealer that runs automatically the moment any consumer of the package boots. The dropper registers itself in composer.json under autoload.files, so no class instantiation or method call is needed - the payload triggers on every PHP request. It harvests AWS, Azure, GCP, Kubernetes, HashiCorp Vault, Jenkins, GitLab, GitHub Actions, CircleCI, browser data, password-manager vaults, SSH keys, crypto wallets, and VPN configs, then AES-encrypts the bundle and exfiltrates to flipboxstudio[.]info/exfil. The script then deletes itself to limit forensic recovery.

Check
Audit composer.lock files and Laravel deployments for any laravel-lang/* package installed since 2026-05-15. Search egress logs for traffic to flipboxstudio[.]info. Check src/helpers.php for unfamiliar code.
Affected
Any PHP application that pulled in a compromised laravel-lang package via Composer. The autoload trigger means the payload runs on every request, not just on first use.
Fix
Roll back to a known-clean laravel-lang version and pin via composer.lock. Rotate every cloud credential, SSH key, browser-stored token, and password-vault item reachable from affected hosts.