dbcve.org
Diskstation ManagerOperating system · Synology

CVE-2024-45538

CRITICAL · 9.6 CVSS v3.1 Published 2025-12-04
Fix available
A fix is available. Upgrade to 3.1.4-23079 / 7.2.1-69057-2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Cross-Site Request Forgery (CSRF) vulnerability in WebAPI Framework in Synology DiskStation Manager (DSM) before 7.2.1-69057-2 and 7.2.2-72806 and Synology Unified Controller (DSMUC) before 3.1.4-23079 allows remote attackers to execute arbitrary code via unspecified vectors.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

Cross-Site Request Forgery (CSRF) vulnerability in the WebAPI Framework of Synology DiskStation Manager (DSM) and Synology Unified Controller (DSMUC) allows remote attackers to execute arbitrary code by tricking authenticated users into submitting malicious requests via unspecified vectors.

MitigationApply the vendor-provided patches (DSM 7.2.1-69057-2 or 7.2.2-72806+, DSMUC 3.1.4-23079+) which implement proper CSRF token validation and SameSite cookie attributes in the WebAPI framework to prevent unauthorized code execution.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Diskstation ManagerOperating system
Affected:>= 7.2.1-69057, < 7.2.1-69057-2>= 7.2.2-72803, < 7.2.2-72806
Diskstation Manager Unified ControllerOperating system
Affected:>= 3.1-23028, < 3.1.4-23079

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check DSM version
    Log into DSM as admin, go to Control Panel > Update & Restore > DSM Update, or run `cat /etc/VERSION` on the device to view the installed build number
    Affected if The build number falls within 7.2.1-69057 through 7.2.1-69057-1 (exclusive of 7.2.1-69057-2) OR 7.2.2-72803 through 7.2.2-72805 (exclusive of 7.2.2-72806)
  2. Check DSMUC version
    If using Synology Unified Controller, access the controller interface and navigate to System Information, or check the version via the controller's web interface
    Affected if The version is 3.1-23028 through 3.1.4-23078 (exclusive of 3.1.4-23079)
  3. Confirm WebAPI framework is accessible
    Verify that the WebAPI endpoint is accessible on your Synology device by attempting to reach `https://[device-ip]/webapi/query.cgi?api=SYNO.API.Info&version=1&method=query` or checking if WebAPI modules are enabled in Control Panel > Application Portal > Web Services
    Affected if The WebAPI returns a valid JSON response indicating available APIs, meaning the framework is enabled and reachable

If the installed DSM or DSMUC version falls within the affected ranges AND the WebAPI framework is accessible, the environment is vulnerable to CSRF-based arbitrary code execution.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 3.1.4-23079 / 7.2.1-69057-2 / 7.2.2-72806 or later
Fixed in 3.1.4-230797.2.1-69057-27.2.2-72806
Interim mitigation

Apply the vendor-provided patches (DSM 7.2.1-69057-2 or 7.2.2-72806+, DSMUC 3.1.4-23079+) which implement proper CSRF token validation and SameSite cookie attributes in the WebAPI framework to prevent unauthorized code execution.

Recommended fix High confidence

DSM 7.2.1-69057-2, DSM 7.2.2-72806, or DSMUC 3.1.4-23079 depending on current installation

  1. 1. Identify current DSM or DSMUC version in Control Panel > System > Update & Restore
  2. 2. For DSM 7.2.1-xxxxx: Upgrade to version 7.2.1-69057-2 or later
  3. 3. For DSM 7.2.2-xxxxx: Upgrade to version 7.2.2-72806 or later
  4. 4. For DSMUC 3.1-xxxxx: Upgrade to version 3.1.4-23079 or later
  5. 5. Download updates from Synology's download center or use DSM's automatic update feature in Control Panel > Update & Restore
Caveat Standard DSM upgrade - review release notes for any configuration or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Diskstation Manager Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $8,448.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-45538 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2024-45538 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data