The PHP, Nextcloud and Arista vulnerabilities of the past week, and how we respond to them
It was a bad week to be running unpatched software. Three separate critical vulnerabilities were disclosed, and reporting says each has been exploited in the wild: a pair of flaws in the PHP runtime itself, a command injection bug in the Collabora CODE server bundled with Nextcloud, and a SQL injection in Arista VeloCloud Orchestrator.
This post explains what was found, who needs to act, what to do today, and how we at Luminarion Labs handle events like this for ourselves and for the businesses we support. If you only have a minute, read the key points below.
On this page
PHP core remote code execution (CVE-2026-109618 and CVE-2026-109619)
- Affects
- The PHP runtime, and every site built on it
- Fixed in
- 8.5.12, 8.4.27, 8.3.36, 8.2.35
- Exploited
- Attempts reported
- Severity
- CVSS 9.2
The most far-reaching of the three. Two flaws in the core PHP runtime, scored 9.2 on the CVSS scale, are reported to allow unauthenticated remote code execution and memory corruption through ordinary HTTP requests. The problems are described as stemming from how PHP handles out-of-memory conditions and from stale request-owned state, which means an attacker may not need to find a bug in your application at all.
That is what makes this one serious. PHP sits underneath WordPress, Drupal, Laravel, Magento, WooCommerce and a very large number of custom business sites. If your website, shop or internal tool runs on PHP, you are in scope regardless of which framework sits on top.
Exploitation attempts have been reported shortly after details became public, including follow-on activity aimed at harvesting credentials and moving through networks quickly.
What to do
- Check your PHP version on every server, including old staging and forgotten test sites.
- Move to PHP 8.5.12, 8.4.27, 8.3.36 or 8.2.35, or the latest release in your branch.
- If you run an unsupported PHP version, patching may not be an option. Plan a migration and isolate the server in the meantime.
- After updating, restart PHP-FPM or Apache so the new runtime is actually loaded.
Collabora CODE in Nextcloud (CVE-2026-110447)
- Affects
- The built-in CODE server app for Nextcloud
- Fixed in
- A fixed release of the app
- Exploited
- Yes, on the CISA KEV list
- Severity
- CVSS 9.2
The built-in CODE server package used by Nextcloud for online document editing contains an operating system command injection flaw, also scored 9.2. Under specific conditions it allows unauthenticated command execution through a proxy script.
CISA has added it to its Known Exploited Vulnerabilities catalog after attackers were seen dropping web shells onto Nextcloud servers to look around, steal credentials and search for cryptocurrency wallets. That listing is the signal to treat this as urgent rather than routine.
What to do
- Update the Collabora Online built-in CODE server app to a fixed release.
- Consider switching to a separately hosted Collabora server instead of the built-in one, which keeps document rendering away from your file server.
- Look for unexpected PHP files in the app directories, and for unusual requests to the proxy script in your web logs.
Arista VeloCloud Orchestrator SQL injection (CVE-2026-114625)
- Affects
- On-premise VeloCloud Orchestrator
- Fixed in
- 5.2.3.18, 6.1.3.10, 6.4.2.12
- Exploited
- Confirmed by Arista and CISA
- Severity
- CVSS 9.9
A SQL injection in on-premise VeloCloud Orchestrator, scored 9.9, lets someone with network access and a low-privilege read-only account reach privileged functionality. Arista and CISA have both confirmed exploitation in the wild.
This one mostly affects organizations running SD-WAN across multiple branches. If that is you, upgrade to the fixed releases Arista published and review who holds accounts on the orchestrator, because the attack depends on having a foothold.
What to do
- Upgrade to Orchestrator 5.2.3.18, 6.1.3.10, 6.4.2.12 or later.
- Remove unused and shared read-only accounts.
- Keep management interfaces off the public internet and behind a VPN or zero trust gateway.
What to do today if you cannot patch immediately
Sometimes a patch needs testing, a maintenance window or a vendor release that is not out yet. Patching is the fix, but these steps buy you time and cost very little.
- Take the system off the public internet if it does not need to be there.
- Put it behind a web application firewall with the vendor or provider rules enabled.
- Restrict access by IP address, VPN or an identity-aware proxy.
- Turn on and keep logs, then look back over the past two weeks for unusual requests.
- Rotate credentials and API keys that live on the affected server if you suspect any compromise.
- Take a clean, tested backup before you change anything.
How we at Luminarion Labs handle vulnerabilities like these
We do not rely on a single clever tool. We rely on a short, repeatable routine that works the same way on a quiet Tuesday and in the middle of a headline vulnerability.
- First, we know what we run. Every system we build or maintain has a named owner and a record of its platform, version and where it is exposed. When an advisory lands, the question "are we affected?" takes minutes, not days.
- Second, we triage by exposure and exploitation, not by score alone. A flaw on the CISA Known Exploited Vulnerabilities list that sits on an internet-facing server goes to the front of the queue. A high score on an internal system that is not reachable can wait for a planned window.
- Third, we reduce the attack surface by design. Our own website runs on Cloudflare Workers with no PHP and no server to patch, the admin area sits behind Cloudflare Access with the token verified again inside the application, pages ship no framework JavaScript, and every page carries a strict content security policy. A whole class of week-one emergencies simply does not apply, because the software is not there.
- Fourth, we patch in a controlled way: apply the fix to a staging copy, check the things that matter, take a backup, deploy, then confirm the new version is genuinely running. We write down what we changed and why.
- Finally, we tell clients plainly. If something affects you, you hear from us with what it is, whether you are exposed, what we are doing and when it will be done, without jargon and without panic.
Building so there are fewer emergencies
Headline vulnerabilities will keep arriving. What changes the outcome is the groundwork done beforehand.
- Keep an inventory of software, versions and owners, and review it regularly.
- Prefer managed and serverless platforms where the provider patches the runtime for you.
- Keep admin areas off the public internet and protect them with strong identity checks.
- Automate dependency and runtime update checks, and subscribe to advisories for what you use.
- Test your backups by restoring them, not just by taking them.
- Agree in advance who decides, who patches and who communicates.
Frequently asked questions
Am I affected by the PHP vulnerabilities if I use WordPress?
Very likely, if your host runs an unpatched PHP version. WordPress runs on PHP, so the fix is to have your host or server administrator update PHP to a patched release. Ask them which PHP version your site uses and when it was last updated.
What does remote code execution mean in plain English?
It means an attacker can make your server run commands of their choosing from somewhere else on the internet. From there they can steal data, install malware or use your server to attack others.
What is the CISA Known Exploited Vulnerabilities catalog?
It is a public list from the US cybersecurity agency of flaws that are confirmed to be used in real attacks. If a vulnerability in software you run is on it, treat patching as urgent.
How quickly should a critical vulnerability be patched?
For internet-facing systems with confirmed exploitation, as soon as you safely can, ideally within days and often within hours. For systems that are not exposed, a planned window is usually reasonable. Reduce exposure first if you cannot patch at once.
Does Luminarion Labs offer security reviews and ongoing maintenance?
Yes. We help businesses in Jamaica, the Caribbean and the UK to audit what they run, plan upgrades, harden websites and applications, and handle updates on an ongoing basis. Book a call and we will tell you honestly where you stand.
Sources and further reading
- CISA Known Exploited Vulnerabilities catalog
- The PHP Group, releases and security announcements
- The Hacker News, vulnerability coverage
Details are drawn from public reporting at the time of writing. Always confirm affected versions and fixes with your vendor before acting.