Audio StationApplication · Synology

CVE-2015-9104

MEDIUM · 5.4 CVSS v3.0 Published 2017-06-30
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
58/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
Cross-site scripting (XSS) vulnerabilities in Synology Audio Station 5.1 before 5.1-2550 and 5.4 before 5.4-2857 allows remote authenticated attackers to inject arbitrary web script or HTML via the album title.

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

A stored cross-site scripting (XSS) vulnerability in Synology Audio Station versions 5.1 before 5.1-2550 and 5.4 before 5.4-2857 allows authenticated users to inject malicious JavaScript or HTML code into the album title field. When other users view the affected album, the injected payload executes in their browsers.

MitigationApply the vendor security update to Synology Audio Station 5.1-2550 or 5.4-2857 or later to patch the XSS vulnerability in the album title input field.

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
Audio StationApplication
Affected:= 5.1-2541= 5.1-2542= 5.1-2547= 5.1-2549= 5.4-2852= 5.4-2853= 5.4-2855

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

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

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. Verify Synology Audio Station is installed
    Check the DSM package manager or list installed packages to confirm Audio Station is present on the Synology NAS.
    Affected if Audio Station is not installed on the system, the vulnerability does not apply.
  2. Determine the installed Audio Station version
    Access the DSM package center, click on Audio Station, and note the version number displayed; alternatively, check via command line using 'synopkg list' or the package info in the DSM interface.
    Affected if The installed version matches 5.1-2541, 5.1-2542, 5.1-2547, 5.1-2549, 5.4-2852, 5.4-2853, or 5.4-2855, indicating the system is running a vulnerable version.
  3. Confirm the album title feature is accessible
    Launch Audio Station and navigate to the music library section where albums are displayed; verify that album titles can be viewed and that the application handles album metadata.
    Affected if The album title functionality is not used or accessible, the XSS payload cannot be triggered.
  4. Inspect album titles for suspicious content
    In Audio Station, review the album list for any entries containing unusual characters such as <script>, javascript:, onload, or other HTML/JavaScript tags in the album title field; alternatively, query the database directly if CLI access is available.
    Affected if Any album title contains embedded HTML script tags or JavaScript event handlers, indicating active exploitation of this stored XSS vulnerability.

The system is affected if Synology Audio Station is installed with a version matching 5.1-2541, 5.1-2542, 5.1-2547, 5.1-2549, 5.4-2852, 5.4-2853, or 5.4-2855, or if any album title contains malicious script injection code.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Apply the vendor security update to Synology Audio Station 5.1-2550 or 5.4-2857 or later to patch the XSS vulnerability in the album title input field.

Fix this in Audio Station Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-2015-9104 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