Preload #03 ·
Patch PHP2Shell, WordPress 7.2 beta, Firefox 159
Also: a six-hour Google Cloud outage, Safari 27 against email-based tracking, and a new Claude API version.
Hard to miss last week's news: PHP, the most widely used server-side language, fixed two critical flaws affecting every installation. A third one has been announced, while the number of published vulnerabilities keeps breaking records. A single Google Cloud zone also showed what one power failure can do to an entire region. Between updates, there was good news too: Firefox 159 makes scroll animations work everywhere, and WordPress 7.2 is in beta.
Enjoy the read, and may your servers hold up this week.
The essentials
- PHP2Shell: update PHP itself, your CMS can't fix it for you.
- WordPress 7.2 is in beta, with the final release due December 8.
- With Firefox 159, CSS scroll-driven animations become Baseline.
Web platform
CSS scroll-driven animations become Baseline with Firefox 159
From October 27, you can tie a CSS animation to scrolling in every major browser, without JavaScript: Firefox 159 turns on scroll-driven animations by default, already available in Chrome 115 and Safari 26. The animation-timeline property, with the scroll() function (a container's scroll progress) and the view() function (an element's position in the visible area), plus the animation-range property, cover reveal-on-scroll, reading progress bars and parallax, which used to rely on AOS, GSAP ScrollTrigger or hand-written scroll listeners.
Baseline, newly available: Chrome 115, Safari 26, Firefox 159
Next step
Find the scroll effects still driven by JavaScript and rewrite them with animation-timeline, animating only transform and opacity, which stay off the main thread. Turn them off under prefers-reduced-motion and keep them as a progressive enhancement, for instance inside an @supports (animation-timeline: view()) block, so older browsers show the content without the effect.
This is a good time to drop a JavaScript library that ships on many brochure sites, and get a smoother effect that frees up the main thread.
Safari 27 blocks services that track visitors by their email address
Your attribution and audience numbers may shift without you shipping anything: in iOS, iPadOS, macOS and visionOS 27, Safari cuts network access to third-party “identity resolution” infrastructure, WebKit announced on October 19. These services grab the email address typed at sign-in or sign-up and turn it into an opaque tracking identifier, so they can follow the person across sites and devices. The block works at the domain level, so reshaping the request won't get around it, and WebKit doesn't name any service.
Next step
If attribution, audience matching or third-party requests drop, compare Safari with other browsers first, before blaming the site or its performance. In a third-party audit, count what Safari blocks separately.
Performance
Chrome measures the weight of ads, with two blind spots
Ads often slow down the pages that show them, without anyone knowing exactly which ones. Chrome can now recognize them (using EasyList, a public ad filter list, and the script that loads them), and DevTools, the browser's built-in diagnostic tool, shows them in an Ads tab: processing time and download size per ad, and a list of ad scripts. Google also publishes four metrics measured on real visitors (screen space taken, count, processing, size) for sites that declare their ad sellers in their ads.txt file.
Next step
On a page with ads, open DevTools (F12 key), Application panel, Ads tab: you'll see which ads and scripts weigh the most. Then cross-check with the Performance panel to find which ones make the page slow to respond to clicks.
Two blind spots in our tests: an ad script running directly in the page isn't counted, only ad frames are, and a Chrome driven by a testing tool shows everything at 0. The script list is therefore more reliable than the total for knowing which ad network slows the site down.
A six-hour Google Cloud outage exposes multi-zone setups without spare capacity
On October 20, from 7:00 to 13:10 London time, Google Cloud's europe-west2-b zone in London lost power, and more than 40 Google Cloud products were affected. According to the preliminary report of October 22, after the grid outage, both the primary and backup controllers failed to start the generators and the UPS batteries ran out; the traffic shifted to the region's two other zones then overloaded them (timeouts, 500 and 503 errors). Revolut was disrupted the same morning without naming a cause; the link to Google rests on an anonymous source quoted by Reuters.
Next step
Check that your critical services run across several zones with enough spare capacity to absorb the loss of a whole zone. For a service that can't go down, consider a second region.
Spreading across zones isn't enough if the remaining ones can't take the load of the zone that fails. Beyond that, relying on a single provider is a concentration risk, to weigh against the cost of a multi-region architecture.
CMS
WordPress 7.2 beta: the admin loads its files separately and encrypts API keys
WordPress 7.2, in beta 1 since October 20 and due December 8, brings two changes your servers and plugins may notice. The admin no longer concatenates its scripts and styles through load-scripts.php and load-styles.php: files now load separately, so the browser caches them better, and those for the next screen are preloaded. The new Secrets API encrypts API keys in the database with the WP_SECRETS_KEY key, or failing that with a key derived from the salts in wp-config.php; the release also adds capabilities to the Abilities API and text-shadow in theme.json.
Next step
Test the beta on a staging site and review any server or firewall rules that target load-scripts.php. Define WP_SECRETS_KEY in wp-config.php before the first secret is stored.
Setting this key matters: without it, simply rotating the salts would make every stored secret unreadable.
AI agents on WordPress: the REST API succeeds where MCP Adapter still fails
If you hand WordPress maintenance to an AI agent, the access channel matters as much as the agent: the independent WordPress Agent Benchmarks, started by Andy Peatling, ran 21 small-business requests (launch, upkeep, migration) through Claude Code and Codex in October, each one twice on the same site. Through the REST API with an application password, 33 of 42 runs succeeded; through MCP Adapter alone, none did, for lack of abilities (the actions WordPress exposes to agents), since core only ships three, all read-only. Even so, WooCommerce 11.3, in beta since October 26 and due November 10, removes its /wp-json/woocommerce/mcp endpoint (it will return 410) in favor of MCP Adapter, served at /wp-json/mcp/mcp-adapter-default-server.
Next step
If an MCP connection still uses the old WooCommerce endpoint, switch it to /wp-json/mcp/mcp-adapter-default-server before 11.3 ships on November 10, and revoke the old REST keys it relied on. To put an agent to work today, give it the REST API with an application password instead.
The tooling isn't mature enough yet, even though the WordPress AI team has made abilities its priority. For now, nothing beats the REST API: it's the approach we favor internally.
Languages and frameworks
php-rust: PHP rewritten in Rust already runs WordPress, just more slowly
The open source project php-rust reimplements PHP 8.5 in Rust, without reusing the Zend Engine's C code, with memory safety as the goal: Rust rules out use-after-free bugs and buffer overflows by design, two classes of flaws in the C engine. It runs WordPress 7.0.1 on a real MySQL and passes the core PHPUnit suite (30,472 tests single-site, 31,278 multisite), along with Composer, PHPUnit and Symfony's http-kernel; Laravel is next. It's still slower than official PHP: about 1.77 times the CPU on the WordPress suite, and 2.4 to 4.6 times on micro-benchmarks.
Next step
Keep it out of production and watch it as a lead; if you maintain a PHP plugin or library, running its test suite on it will show you where behavior differs.
Faster performance is a goal, not a given; the real value is memory safety, and parity on the WordPress suite is already a serious result.
AI and dev tools
Claude API: the first new version since 2023 breaks existing calls
If your tools call the Claude API, moving to the new SDKs can break your requests: on October 21, Anthropic released API version 2026-10-21, the first since 2023-06-01, and new major SDKs send it by default (Python 2.0, TypeScript 1.0, PHP 1.0, Go 2.0, among others). In this version, temperature, top_p and top_k return a 400 error, even at their default values, and the SDKs send the key in Authorization: Bearer instead of X-Api-Key. No end date has been announced for 2023-06-01.
Next step
Remove temperature, top_p and top_k from your calls, and update your proxy, gateway and log filters for the Authorization header. In PHP, composer update stays within your version constraint: use composer require to get 1.0, then replace MessageParam with the per-role classes, or you'll hit a TypeError.
Check your log filters first: masking set up for
X-Api-Keywould let the key through in plain text in the new header.
An AI agent can now analyze an application's memory leaks
For a single-page application (SPA) whose memory keeps growing during a session, chrome-devtools-mcp 1.12.0, the MCP server that gives an AI agent access to Chrome DevTools, can analyze a heap snapshot (a snapshot of the JavaScript memory heap) without a connected browser since October 22, with paginated results. The release also runs independent tool calls in parallel, hot-reloads its configuration with --watchConfig and masks WebSocket headers in its logs. On the DevTools side, the Memory panel now flags unused closure variables kept alive by a shared V8 context, sorted by memory impact.
Next step
Take a heap snapshot in the Memory panel, have your agent analyze it through this server, then check its findings with the Objects retained by contexts filter.
Security
PHP2Shell: update PHP itself, not just your CMS
Every PHP site stays exposed until its server runs PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, released October 21: they fix CVE-2026-109618 and CVE-2026-109619 (“PHP2Shell”), an unauthenticated remote code execution flaw in the engine, scored 9.2 in CVSS 4.0, whatever the application. Found by Wiz Research, OpenAI Codex Security and Calif with the help of AI models, the flaws saw an exploitation attempt spotted by Amazon as early as October 17, before disclosure. A third flaw, CVE-2026-115560, with an unlikely attack vector, will be fixed in the next regular release; PHP 8.1 and older get no new release, only minimal patches published as source.
Next step
Update PHP (updating WordPress, Drupal or PrestaShop fixes nothing, and WordPress.org has no update planned), then restart PHP-FPM, Apache and long-running PHP processes; on shared hosting, ask your host. Set session.upload_progress.enabled=0 in php.ini or the pool config, never with ini_set(). On Plesk, the panel's own PHP needs 18.0.81 Update 4 or 18.0.80 Update 11.
A site still on PHP 8.1 or older can be patched this time, thanks to backports from Ondřej Surý's repository (a fixed PHP 7.4 package on October 21) or from Plesk. That's neither an official nor a lasting solution: nothing guarantees the next fix, so now is the time to plan the migration.
Published vulnerabilities nearly doubled in 2026: triage from your inventory
The volume of vulnerabilities to track can no longer be handled by hand: according to the NVD, the US government's vulnerability database, 86,554 CVEs were published in 2026 as of October 26, against 48,151 for all of 2025. On October 21, the day of the PHP2Shell fixes, Node.js 26.12.1, 24.22.1 and 22.23.4 also fixed ten vulnerabilities.
Next step
List the building blocks you actually run in production (PHP, Node.js, web server, hosting panel) and subscribe to those projects' security lists. Prioritize with CISA's KEV catalog (exploited vulnerabilities) and EPSS (likelihood of exploitation) rather than the CVSS score alone.
The bottleneck is no longer discovery, which AI speeds up, but patching: automate updates and shrink your exposed surface.
Certificate authority keys exposed: Chrome and Firefox drop eMudhra
A valid TLS certificate could be forged for any domain: on October 17, the private keys of eight intermediate certificates from the Indian authority eMudhra, six of them for TLS, turned out to be recoverable (flawed generation, keys too small). Chrome blocked them that evening through CRLSet and announced it will remove the affected eMudhra root, Firefox revoked them through OneCRL, and Mozilla is urgently removing emSign ECC Root CA G3. eMudhra estimates around 30,000 certificates need to be migrated.
Next step
Update the certificate stores on your servers, Docker images and runtimes (Node.js did so on October 21), then redeploy. If one of your sites uses an emSign certificate, switch authorities, and never turn off TLS verification to work around an error.
Duplicator: a flaw means rebuilding your old migration packages
Duplicator and Duplicator Pro, active on more than a million WordPress sites, are hit by CVE-2026-82814 (8.8 in CVSS 3.1), an unauthenticated PHP object injection (crafted data that PHP rebuilds into an object), published by Wordfence on October 20. The crafted value is planted in a comment and fires when an administrator builds a package containing it and then migrates with the installer, leading to command execution (free version) or a file deletion that enables a site takeover (Pro). The flaw has been fixed since 5.0.0, released September 8, but a package built earlier keeps the vulnerable installer.
Next step
Make sure Duplicator is on 5.0.0 or later, then delete packages built before that version and rebuild the ones you need.
Finds
Arachnide, a free technical SEO crawler that runs locally
To audit a site's technical SEO without a license or an account, Thierry Gustin has released Arachnide, an open source crawler (MIT license) that runs locally on Node.js 18.17 or later. It runs about 90 checks (redirects, canonicals, hreflang, JSON-LD, sitemaps, click depth) and turns them into an action plan ranked by impact and effort, exportable as CSV or as an HTML report you can print to PDF, with a CLI and an interface in six languages, French included. The default budget is 500 pages, and JavaScript rendering is optional.
Next step
Run it on a site you know well and compare with your usual tool. For a site whose pages are built in JavaScript, turn on rendering through an installed Chrome or Edge, or it will see them as empty, and raise the 500-page budget for a large site.
It's a free alternative to Screaming Frog for everyday audits; the project is young and maintained by a single author, so put it through its paces before making it a whole team's tool.
opendesk, an open source helpdesk you can host yourself
To keep your support data in house, Mindroot has released opendesk, an open source helpdesk (Apache 2.0): shared support inbox, embeddable chat widget, public help center, AI (Anthropic, OpenAI-compatible models or a local model), API, webhooks and an MCP server. Written in Go and Elixir on Postgres, it self-hosts with a single command (Docker, Caddy) and runs the same code as the cloud offering. The project is new, and neither the widget's weight nor how it loads is documented.
Next step
If you embed the widget, load it on click behind a facade (a lightweight button that only loads the real script on interaction) and reserve its space to avoid CLS. An iframe doesn't isolate INP or CLS: measure it like the rest of the page.
Self-hosting settles the data sovereignty question, not the widget's cost to your site, which you should measure before rolling it out.