“It’s just our file server.” Plenty of small firms say this about Nextcloud. It’s the private alternative to Dropbox or SharePoint, it sits on a box in the closet or a rented server, and it mostly takes care of itself.
Here is the problem: if someone installed the add-on that lets staff edit Word and Excel files in the browser, that server may have had an unlocked side door since early September. Attackers found it before most owners did.
What actually happened
Nextcloud can open and edit Office documents through Collabora Online. The simplest way to set that up is a Nextcloud app called “Collabora Online – Built-in CODE Server” (its technical name is richdocumentscode). It runs a small Collabora server inside Nextcloud itself, with no separate machine to manage. That convenience is why small offices pick it.
Versions before 26.4.303 contain a command injection flaw in a file called proxy.php. When the built-in document server isn’t running, which happens after a restart, an upgrade or a crash, an attacker can send a crafted web request and run commands on the server. No password or user click is needed. NVD scores it 9.8 out of 10, and the CVE record’s own score is 9.2.
Here is the timeline, based on the CVE record, the project’s public issue tracker and the Nextcloud community advisory:
- September 10: Administrators logged the first malicious requests and found PHP web shells (small backdoor scripts with names like
shx5cf91.php) in the app’s folder. - September 11: Collabora released the fix in version 26.4.303.
- October 3: A Nextcloud community post urged built-in users to update as soon as possible because the flaw was already being exploited.
- October 14: The CVE and formal advisory were published.
- October 23: CISA added CVE-2026-110447 to its Known Exploited Vulnerabilities catalog and gave federal agencies until October 26 to fix it.
That’s about five weeks between a quiet fix and a public warning. Collabora largely blamed a CVE processing backlog. Nextcloud said the fix was in its app store and it hadn’t seen widespread exploitation. Either way, a firm that doesn’t update apps routinely may not have known it needed to.
What the attackers did, and what’s still unclear
In the incidents administrators shared publicly, the attackers planted a web shell and then searched for password manager databases, cryptocurrency wallets and key files. Reports also describe them going after configuration files that hold credentials. One administrator only noticed because the server started emailing about failed attempts to gain admin rights.
The reports we reviewed showed no evidence that attackers gained full root control, and no clear sign of files being copied off the server. That’s reassuring but limited. The web shell runs with the same access as Nextcloud, so anything Nextcloud can read should be treated as possibly exposed. For most firms, that’s the client files.
How many servers were hit is unknown. Some posts online say ransomware groups are using this flaw. BleepingComputer couldn’t confirm that, and we didn’t find a primary source that does, so treat it as unverified for now.
Not everyone is affected. According to Collabora and Nextcloud, standalone Collabora servers, Collabora run in Docker or from a Linux package, hosted Collabora services and Nextcloud All-in-One setups are not vulnerable. Firms that use Nextcloud without document editing aren’t affected either. The risk sits with the do-it-yourself setup that small offices tend to choose.
Why this one matters for smaller firms
Self-hosted file sharing is popular with accounting firms, law offices, engineering shops, contractors and medical practices, often to keep sensitive files off big cloud platforms. But a self-hosted server only stays safe if someone patches it, and in a small firm that may be a part-time IT contractor who set it up years ago.
Restarts and upgrades, the routine events that open the door, happen all the time. And turning the app off isn’t enough: Collabora warns that a disabled app’s files can still be reached.
What to do this week
- Find out if you run it. Ask whoever manages Nextcloud to check the app list (or run
occ app:list) for “Built-in CODE Server” /richdocumentscode. - Update to 26.4.303 or later, or uninstall it. After removing it, confirm the
apps/richdocumentscodefolder is actually gone. - Look for web shells. Search that folder for unexpected PHP files, especially names starting with
shx, and runocc integrity:check-app richdocumentscode. - Check the logs back to September 10 for requests to
proxy.phpcontaining odd characters like$(or${IFS}. - If you find anything, stop and call before you clean. Preserve the logs and files, contact your cyber carrier’s hotline or your broker, and then rotate the database password, mail credentials, storage keys and any passwords stored on that server.
- If you’re on Nextcloud 29 or older, you’re on an end-of-life version. Plan the upgrade now.
Where cyber insurance fits
This is our read, not a coverage opinion. Your actual policy wording, endorsements and declarations control.
If a web shell turns up, a cyber policy is built for what comes next: forensic investigators to determine what was accessed, breach counsel to decide whether clients or patients must be notified, and the cost of restoring or rebuilding the server. Calling the carrier’s breach line before you wipe anything protects both the evidence and your claim.
The harder question is patching. Applications ask how quickly you apply critical updates, and some policies now include conditions, exclusions or reduced limits for losses from known vulnerabilities left unpatched past a set window. A flaw that had a fix in September and sat on CISA’s list in October is exactly what those provisions describe. Find out whether your policy has one and what the clock is.
Stolen credentials are the other gap. If a password lifted from that server later leads to a fraudulent wire or a redirected payment, that loss often falls under social engineering or funds transfer coverage, which many policies cap well below the main limit.
Your file server doesn’t have to be famous to be found. It just has to be behind on updates.
Sources
- NVD: CVE-2026-110447
- CISA: Known Exploited Vulnerabilities Catalog entry, added October 23, 2026
- Nextcloud Community: To Collabora Built-in users, update ASAP
- Collabora richdocumentscode issue tracker: exploitation reports and maintainer guidance
- BleepingComputer: Hackers exploit Collabora RCE flaw to backdoor Nextcloud servers
- eSecurity Planet: Hackers Use Critical Collabora Flaw to Compromise Nextcloud Servers