dbcve.org
Router ManagerOperating system · Synology

CVE-2024-53280

MEDIUM · 5.9 CVSS v3.1 Published 2024-12-09
Fix available
A fix is available. Upgrade to 1.3.1-9346 or later.
See remediation →
63/100
Remediation priority · Elevated
Remotely reachable

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
Improper neutralization of input during web page generation ('Cross-site Scripting') vulnerability in network center policy route functionality in Synology Router Manager (SRM) before 1.3.1-9346-10 allows remote authenticated users with administrator privileges to read or write specific files containing non-sensitive information and conduct limited denial-of-service attacks by injecting arbitrary web script or HTML.

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 · high confidence

Cross-site scripting (XSS) vulnerability in the network center policy route functionality of Synology Router Manager allows authenticated administrators to inject arbitrary web script or HTML via unsanitized input, potentially enabling limited file read/write of non-sensitive data and limited denial-of-service conditions.

MitigationUpgrade Synology Router Manager to version 1.3.1-9346-10 or later to address the XSS vulnerability in the policy route feature.

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
Router ManagerOperating system
Affected:>= 1.3, < 1.3.1-9346= 1.3.1-9346

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
High
User interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
Low

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

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. Identify installed SRM version via web interface
    Log into Synology Router Manager (SRM) web interface, go to Control Panel > System > Info, and locate the 'Software' section showing the version number
    Affected if Version is 1.3.0 through 1.3.1-9345 (any build before 1.3.1-9346), or exactly 1.3.1-9346
  2. Identify installed SRM version via command line
    Access the router via SSH and run: `cat /etc/VERSION` or `cat /etc.defaults/VERSION` to retrieve the exact firmware build number
    Affected if The displayed version string falls within the range >= 1.3 and < 1.3.1-9346, or equals 1.3.1-9346 exactly
  3. Verify policy route feature configuration
    In SRM web interface, navigate to Network Center > Policy Route and check if any policy routes are defined or if the feature is accessible
    Affected if Policy route feature exists and is accessible to the administrator account (vulnerability requires authenticated admin access)
  4. Confirm administrator access to network settings
    Log into SRM as an administrator and verify access to Network Center settings where policy route configuration is located
    Affected if Administrator account has permissions to configure policy routes - the XSS payload would be injected through this interface

You are affected if your Synology Router Manager version is 1.3.0 through 1.3.1-9345 or exactly 1.3.1-9346, and you have an administrator account that can access the Network Center policy route feature.

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 1.3.1-9346 or later
Fixed in 1.3.1-9346
Interim mitigation

Upgrade Synology Router Manager to version 1.3.1-9346-10 or later to address the XSS vulnerability in the policy route feature.

Recommended fix High confidence

1.3.1-9346-10

  1. 1. Log into the Synology Router Manager (SRM) web interface.
  2. 2. Navigate to Control Panel > System > Update & Restore.
  3. 3. Check the current SRM version under the System Information section.
  4. 4. If the installed version is < 1.3.1-9346-10, navigate to the DSM update section and apply the update to version 1.3.1-9346-10 or later.
  5. 5. Alternatively, download the latest SRM update from the Synology Download Center and manually install it via Control Panel > System > Update & Restore > Manual Update.
  6. 6. After the update completes, verify the new version is 1.3.1-9346-10 or higher.

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

Fix this in Router Manager Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2024-53280 — 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-53280 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