Since September 2026, attackers have been quietly planting PHP web shells on Nextcloud servers through an optional office app most administrators installed once and forgot. The culprit is CVE-2026-110447, an unauthenticated OS command injection in the Collabora Online – Built-in CODE Server app. And the detail everyone gets wrong: disabling the app does not fix CVE-2026-110447. You must upgrade it or remove it entirely.
CVE-2026-110447 at a Glance
CVE-2026-110447 is an OS command injection vulnerability (CWE-78) in proxy.php of the richdocumentscode app — the “Collabora Online – Built-in CODE Server” that runs a lightweight document server inside Nextcloud. A crafted request can make the server execute operating system commands as the web server user, with no account and no user interaction. It carries a CVSS score of 9.2. It affects all app versions before 26.4.303; Collabora shipped the fix in version 26.4.303 on September 11, 2026. There is one unusual precondition: the built-in CODE server process must not be running when the malicious request arrives. That window opens during perfectly routine events — a container restart, an upgrade, or a crash — which is why exploitation has succeeded in the wild since at least September 10. Post-exploitation reporting describes attackers dropping web shells and then searching the server for password databases, password-manager files and cryptocurrency wallet data. Standalone Collabora Online servers, Docker- or package-based Collabora setups, and Nextcloud All-in-One are not affected by CVE-2026-110447. Note that the fixed app requires Nextcloud 30 or later: Nextcloud 29 and older are end-of-life, yet the app store still serves those servers a vulnerable version.

Am I Affected by CVE-2026-110447?
You are affected only if the Built-in CODE Server app is installed at a version below 26.4.303. From your Nextcloud directory, check with occ (adjust the web user to your setup):
sudo -u www-data php occ app:list | grep -A1 richdocumentscode
The app’s version is also shown under Settings → Apps → Office & Text in the admin interface. If richdocumentscode is absent, CVE-2026-110447 does not apply to you. If it is present and old, assume your server has been reachable through every restart window since September — patch it and then hunt, in that order.
How to Patch CVE-2026-110447 Step by Step
Step 1 — Update the app to 26.4.303 or later:
sudo -u www-data php occ app:update richdocumentscode
Step 2 — Or remove it entirely if you do not need built-in document editing (the safer option for servers you rarely touch):
sudo -u www-data php occ app:remove richdocumentscode
Remember: occ app:disable is not a fix for CVE-2026-110447 — Collabora’s advisory is explicit that the vulnerable code remains reachable. On Nextcloud 29 or older, upgrade Nextcloud itself to a supported release, or remove the app, because no fixed app version exists for EOL platforms. If your Nextcloud runs in containers, the same discipline applies as for any self-hosted stack like the one in our Docker Compose LEMP guide: know every component you run, and know its version.
Step 3 — Verify the app version again with occ app:list and confirm document editing still works if you kept the app.
Temporary Mitigations for CVE-2026-110447
There is no partial mitigation that Collabora endorses. Until the update or removal is done, your only real options are to take the Nextcloud instance off the public internet (VPN or IP allowlist) or accept a known, actively exploited risk. Keep restarts and upgrades of the CODE app to a minimum in the meantime, since each stop of the built-in server opens the exploitation window wider.
Detection: Web Shells and Other IoCs
Attackers exploiting CVE-2026-110447 have left a distinctive calling card: PHP files named like shx*.php inside the app directory. Hunt for them and for any PHP file that does not belong:
find /var/www/nextcloud/apps/richdocumentscode -name "shx*.php"
find /var/www/nextcloud -name "*.php" -newer /var/www/nextcloud/version.php
(Adjust the Nextcloud path to your installation.) Also review web server logs for suspicious requests to the app’s proxy.php, check for Nextcloud admin accounts you did not create, and look for unusual outbound connections. Save copies of anything suspicious for investigation before deleting it. If you find a shell, updating is no longer enough: everything the web server account could read must be treated as exposed, so rotate the Nextcloud database password, stored app credentials and user passwords, and review files that were accessible. Reporting collected by Cybersecurity News on the Collabora exploitation campaign describes the same shell-planting pattern across victims.
Also schedule a recurring reminder to review your installed Nextcloud apps — all of them, not just this one. Optional apps are the most commonly forgotten attack surface on self-hosted platforms: they are installed for one feature, they execute with broad permissions, and their update cadence depends entirely on an administrator remembering they exist. A quarterly inventory of apps, versions and end-of-life status would have caught CVE-2026-110447 exposure in minutes, and it will catch the next one too.
Conclusion
CVE-2026-110447 is a reminder that optional apps are still attack surface — especially ones that execute commands. Update richdocumentscode to 26.4.303 or remove it today, and do not let “I disabled it” be the end of the story. Then check for shx*.php before you call it done.