Most websites and business apps run on a handful of common technologies, and several of them shipped important security fixes between 16 and 21 November. A few older fixes are included below as dated reminders, because many sites still haven’t applied them. Some of the problems below let an attacker take over a server without logging in. Here is a plain summary of what matters, what to update and what to do if you can’t update yet.
PHP and WordPress
PHP 8.5.13, 8.4.28, 8.3.37 and 8.2.36
On 19 November the PHP team released updates that fix 18 vulnerabilities. The most serious, CVE-2026-129289, is a flaw in PHP-FPM with a critical severity score of 9.2. In short, an attacker can sneak a second, forged request through the web server and run their own PHP code. It only works when the web server keeps connections to PHP-FPM open and reuses them (nginx with fastcgi_keep_conn on, or Apache with enablereuse=on). Standard setups that close the connection after each request are not affected by the demonstrated attack.
What to do: update to the fixed release for your branch and restart PHP. If you can’t update today, turn off connection reuse in nginx or Apache. Also make sure PHP-FPM is not reachable directly from the internet.
If you haven’t patched since October, note that a separate pair of PHP flaws known as “PHP2Shell” (CVE-2026-109618 and CVE-2026-109619, both 9.2 under CVSS v4 from the PHP project; NVD’s CVSS v3.1 scores are 9.8 and 8.1) is being exploited in the wild and is on CISA’s Known Exploited Vulnerabilities list. Those were fixed in PHP 8.5.12, 8.4.27, 8.3.36 and 8.2.35, so the versions above cover both. PHP 8.1 and older no longer get official fixes, so plan an upgrade.
Sources: PHP advisory GHSA-qc49-hpvq-g2w6, BleepingComputer, CISA alert
WordPress core: check you are on a patched version
WordPress 7.1.2 (and backports such as 7.0.6, 6.9.9 and 6.8.10) fixed CVE-2026-87902 in September. It is an unauthenticated path traversal that can lead to code execution when the server and the active theme meet certain conditions, and CISA lists it as exploited. It is not new this week, but sites that skip updates are still exposed. What to do: update to WordPress 7.1.5 or the latest release for your branch. 7.1.5 is a further security release from 18 November that fixes, among other issues, an unauthenticated privilege escalation that could lead to code execution. Then turn on automatic security updates.
Sources: WordPress.org release post, GitHub advisory, NVD, WordPress 7.1.5 release post
WordPress plugins to update or remove
Wordfence’s report for 9-15 November counted hundreds of new plugin and theme vulnerabilities, so plugin hygiene is where most WordPress sites get hurt. Four worth acting on:
- Shipo (CVE-2026-19907): versions 1.6 to 1.8.0 let an unauthenticated visitor impersonate a user, including an administrator. Update to 1.8.1 or later.
- Easy DragDrop File Uploader (CVE-2026-124822): versions before 1.1.10 allow unauthenticated deletion of server files, which can include
wp-config.php. Update to 1.1.10 or later. - Masteriyo LMS (CVE-2026-124990): versions up to 3.5.1 have a PHP object injection flaw rated 9.8. Update to 3.5.2 or later.
- Auth Armor Passwordless Login (CVE-2026-110960): versions up to 1.0.3 allow admin takeover and there is no patch. Deactivate and delete it, rotate the Auth Armor API keys and review your logs.
Sources: Wordfence: Shipo, Patchstack: Easy DragDrop, Patchstack: Masteriyo, Wordfence: Auth Armor, Wordfence weekly report, 9-15 Nov
Java and Spring
Spring Security and Spring Boot (19 November)
Spring published a batch of advisories. Two stand out:
- CVE-2026-59273 (critical, Spring Security): a class called
ELRequestMatcherevaluates expressions with no restrictions. If an app binds outside input to a matcher of that type, an attacker could run code. Fixed in Spring Security 7.1.3 and 7.0.9. Fixes for the 6.x and 5.x lines are for Enterprise Support customers only, so older versions may need an upgrade. - CVE-2026-59378 (high, Spring Boot): an authentication bypass on Actuator health paths, but only in Jersey-based apps with a specific path clash. Spring itself expects it to be rare. Fixed in Spring Boot 4.1.3 and 4.0.10. Spring Boot 3.5 and 3.4 are also affected; those fixes (3.5.18 and 3.4.19) are for Enterprise Support customers only.
Sources: spring.io: CVE-2026-59273, spring.io: CVE-2026-59378
“Java4Shell” in OpenJDK (CVE-2026-114938)
Fixed on 17 November, this is a memory bug in Java’s Base64 decoder, rated 8.1 by CERT-EU. It matters only on x86-64 servers with newer AVX-512 CPUs (Intel Ice Lake or later, AMD Zen 4 or later), where attacker-controlled Base64 data, such as a login header or token, can reach the decoder. ARM servers are not affected.
What to do: update to 17.0.21.1, 21.0.13.1, 25.0.5.1 or 27.0.1.1 and restart every Java process. Until then, start the JVM with -XX:+UnlockDiagnosticVMOptions -XX:-UseBASE64Intrinsics.
Sources: CERT-EU advisory 2026-021, Oracle 21.0.13.1 release notes
Laravel, Next.js, React and Node.js
Laravel 12.73.0 and 13.43.0
Laravel fixed eight advisories on 18 November, covering a security-check bypass, denial of service and cross-site scripting. One example: in Laravel 13, an empty form field could hide an uploaded file from validation, letting a file skip type and size rules (rated moderate, 5.3). What to do: update to 12.73.0 or 13.43.0 and re-check any optional file upload fields.
Sources: CERT-FR CERTFR-2026-AVI-1571, GHSA-hxc4-wvjf-r59p
Next.js, React Server Components and Node.js
- Next.js: the 3 November release (16.4.5 and 15.5.29), which came out before this week, fixes seven issues. The Next.js blog rates one as high (cached data leaking between users) and the other six as medium, including HttpOnly cookies becoming readable on Edge routes. Update with
npm install next@16.4.5ornext@15.5.29. Source: Next.js blog - React Server Components (CVE-2026-126187): a critical, unauthenticated code execution bug in
react-server-dom-webpack,-parceland-turbopack. Update to 19.0.9, 19.1.10, 19.2.9 or 19.3.1. Apps with no server-side React are not affected. This is not new this week (GitHub published the advisory on 14 October; NVD lists it from 10 November). Source: GitHub advisory - Node.js: the 11 November releases (22.23.5, 24.22.3 and 26.13.1), just before this week, fix several high-severity HTTP/2 and HTTPS issues, including one that can crash a server and one that can disclose memory from other connections (including TLS keys). Source: Node.js blog
Actively exploited this week
On 18 November CISA added four flaws to its exploited list: Apache Axis (CVE-2026-90436), LiteLLM (CVE-2026-40217), REDCap (CVE-2026-90817) and Synology DiskStation Manager (CVE-2024-10441). If you run any of these products, treat patching as urgent. Source: CISA
A simple checklist
- Update PHP and restart PHP-FPM or Apache.
- Update WordPress core and plugins, and delete plugins you no longer use.
- Update Java runtimes and restart the services that use them.
- Update Laravel, Spring, Next.js, React and Node.js dependencies.
- Keep backups and test them.
Need a hand?
Keeping up with fixes like these is hard when you also have a business to run. Hyrrokkin offers website security checks, ongoing maintenance and monitoring, so updates get applied and problems are caught early. Write to us at support@hyrrokkin.net.