Synology strongly urges all users running vulnerable versions to update DSM immediately. Our advice is to treat that as this week's job, not next quarter's. Then check whether the box can be reached from the internet, and if it can, close that door and give staff a safer way in. Below is how to do each step in plain words, even if you are not the IT person.

For many small offices, that is the small box in the supply closet that holds the shared drive. If your office keeps intake forms, case files, scanned IDs or tax documents on it, this deserves your attention.

What happened, in plain words

The flaw is tracked as CVE-2024-10441, which CISA lists as an Improper Encoding or Escaping of Output Vulnerability in Synology DiskStation Manager (DSM). Synology's security advisory was published on 2024-11-05, and it says the flaw sits in the system plugin daemon and allows remote attackers to execute arbitrary code. In everyday terms: someone on the internet may be able to run their own programs on your file server.

Synology gives it a CVSS3 base score of 9.8 and a Critical severity rating. Check the advisory itself for the current status and for any mitigation listed, and plan to install the fixed version it points to. Affected DSM versions are those before 7.2-64570-4, 7.2.1-69057-6 and 7.2.2-72806-1. Upgrading is the fix.

Here is why we'd move this from "patch when convenient" to "patch now":

9.8
CVSS3 base score from Synology
380,000+
Internet-exposed Synology NAS devices tracked by Shadowserver
None
Mitigation listed by Synology

That middle number is the one to sit with. BleepingComputer reports that the watchdog group Shadowserver now tracks over 380,000 Internet-exposed Synology NAS devices. That doesn't mean every one of them is unpatched, but it does show how many of these boxes answer from the open internet. Our view: attackers don't need to know your office exists. Automated scanning makes any box that answers from the internet a candidate.

Why a file server is such a big target

In our view, attackers like a shared file server for the same reason your office does: everything is in one place. If they get in, they may copy your files before locking them, which leaves you with two problems at once: you can't work, and someone outside may now hold your clients' data.

Talk to your attorney about which rules apply to you; here is what the text of two of them says:

Big organizations are not immune either. The Los Angeles County Department of Public Health disclosed a data breach affecting more than 200,000 individuals, after an attacker gained the login credentials of 53 Public Health employees through a phishing email. That was a different kind of attack, but the lesson carries over: one weak entry point can expose a very large pile of records.

Heads up

If your box has been reachable from the internet and was not updated, treat "update it" as step one, not the whole job. [CISA's BOD 26](https://www.cisa.gov/news-events/alerts/2026/11/18/cisa-adds-four-known-exploited-vulnerabilities-catalog)-04 sets expectations for when federal agencies must check whether threat actors compromised a system before the patch was applied. We think the same question is worth asking in a small office.

Step 1: Find out if your office is affected

You can do this yourself, or forward this section to whoever set up the box.

Check your DSM version

  1. Log in to the Synology from a computer in the office (the same web page you or your IT person use to manage it).
  2. Open Control Panel, then Info Center. Note the DSM version line.
  3. Compare it with the table below. If your version is lower than the fixed one for your branch, treat the box as affected.
Your DSM branchFixed release (or newer)
DSM 7.2.27.2.2-72806-1
DSM 7.2.17.2.1-69057-6
DSM 7.27.2-64570-4
DSM 7.17.1.1-42962-7

Synology's advisory also lists an older DSM 6.2 branch with a "moderate" rating and an upgrade target of 6.2.4-25556-8 or above. If your box is still on that older branch, in our view it is old enough to deserve a bigger conversation about replacing it.

Check whether the box answers from the internet

This is the question that decides how urgent your week is. Ask, or look for, any of these:

Hypothetical: a Westside law office

Hypothetical: a six-person family-law office keeps every client folder on a Synology. Two attorneys reach it from home through a port-forward the previous IT contractor set up, and nobody has logged into the admin page in a year. Their DSM version is below the fixed release. That office is in the highest-risk group: exposed, unpatched, and full of personal information. The right order for them is: cut outside access today, update tonight, check for signs of intrusion tomorrow, then rebuild remote access properly.

Step 2: Install the fixed update

Here is how to do the update, step by step.

  1. Pick a quiet window. Updates usually restart the box. Evening or early morning is best, and tell staff the shared drive will be down for a while.
  2. Make sure you have a backup that isn't on the same box. In our view, a copy on a drive plugged into the box is better than nothing, but a copy that is offline or in a separate cloud account is what gets you back after ransomware.
  3. Go to Control Panel > Update & Restore. Let DSM check for updates and install the newest one offered for your model. Don't stop at "a bit newer"; check your new version against the table above.
  4. Confirm the version afterward in Info Center. Write the date and version down somewhere your office keeps IT records.
  5. Turn on automatic security updates if your model offers them, so the next fix doesn't wait for someone to remember.
Tip

If the update screen says your model can't get the fixed version, stop and get help. An unsupported box that holds client data should not stay reachable from the internet at all.

Step 3: Check that nobody got in first

If the box was exposed and unpatched, updating closes the door but does not tell you whether someone already walked through it. Quick things you or your IT person can look at:

If anything looks wrong, don't start deleting things. Disconnect the box from the network, keep it powered on, and call someone who does incident response. Whoever investigates will want to see what happened, and your attorney will want the facts too.

Step 4: Keep remote access without leaving the door open

Offices usually open their file server to the internet for a good reason: people need files from home, from court, or from a second location across town. The goal is to keep that convenience while taking the login page off the open internet.

Put a VPN or private network in front of it

The safer pattern is simple: the file server answers only inside your office network, and remote staff connect to that network first through a private, encrypted connection before they open the shared drive. To the internet, the box simply isn't there. Then remove the port-forwarding rules on the router.

Turn on the protections DSM already has

We'd switch on these built-in protections:

They make the next problem harder to exploit.

Clean up accounts and sharing

Pitfalls we see offices fall into

A one-page checklist for this week

  1. Find the DSM version in Info Center and compare it with the table above.
  2. Ask whether the box is reachable from outside (port forwarding, remote-access features, mobile apps away from the office).
  3. If it is exposed, cut outside access today.
  4. Confirm a backup exists off the box.
  5. Install the latest update; write down what you installed and when.
  6. Turn on automatic security updates.
  7. Check accounts, logs, tasks and packages for anything unfamiliar.
  8. Rebuild remote access behind a VPN; remove port-forward rules.
  9. Enforce 2FA for admins, turn on Auto Block, set firewall rules.
  10. Note who in the office owns this box from now on.

What we'd do for a Los Angeles office

If we sat down with your office this week, we would confirm the DSM version and exposure first, close outside access the same day, patch, look for signs of intrusion, and then design remote access that works for how your team actually moves around the city, whether that is home, court, or a second clinic location. We'd also make sure one named person "owns" the box going forward, so the next update doesn't depend on someone remembering.

That is the kind of practical, plain-English review we do in an AI and IT consultation: we look at where your client files live, who can reach them, and which tools touch them, then hand back a short, ordered fix list. If your team also wants files to flow into intake or document workflows automatically, we'd build that AI automation work to use only the access it needs. You can read more about how we work with local offices on our Los Angeles page.

Next step

Check your DSM version today and install the update as soon as you can. If you'd rather have someone confirm the box is patched, closed to the internet and still easy for your team to use, book a Free Automation Audit. We'll walk through your file server and remote access with you and give you a plain list of what to fix first.

Sources