CVE-2015-9105
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 · uneditedMultiple cross-site scripting (XSS) vulnerabilities in Synology Video Station 1.2 before 1.2-0455, 1.5 before 1.5-0772, and 1.6 before 1.6-0847 allow remote authenticated attackers to inject arbitrary web script or HTML via the (1) file name or (2) collection name of videos.
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 confidenceStored cross-site scripting (XSS) vulnerabilities in Synology Video Station allow authenticated users to inject arbitrary web script or HTML through video file names or collection names. When other users view these entries, the malicious script executes in their browsers, potentially enabling session hijacking or credential theft.
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= 1.2-0439= 1.2-0443= 1.2-0447= 1.2-0451= 1.2-0453= 1.5-0753= 1.5-0754= 1.5-0757= 1.5-0763= 1.5-0770= 1.6-0835= 1.6-0840CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Synology Video Station is installedAccess Synology DiskStation Manager, open Package Center, and look for Video Station in the installed packages listAffected if Video Station is not installed on the system
-
Identify installed Video Station versionIn Package Center, click on Video Station and view the version number displayed in the package detailsAffected if The installed version matches any of: 1.2-0439, 1.2-0443, 1.2-0447, 1.2-0451, 1.2-0453, 1.5-0753, 1.5-0754, 1.5-0757, 1.5-0763, 1.5-0770, 1.6-0835, or 1.6-0840
-
Verify Video Station library has media filesOpen Video Station and navigate to the video library or collection view to see if any videos or collections existAffected if The Video Station library contains any video files or collections that could have user-supplied names
-
Check for untrusted user access to Video StationReview Video Station user permissions in Control Panel > Shared Folder > Video Station to determine if users other than administrators can access or add contentAffected if Non-administrative users have write access to add or rename videos or collections
The environment is affected if Synology Video Station is installed with a version matching one of the twelve affected releases and the library contains user-controllable video file names or collection names accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 dataUpdate to Synology Video Station version 1.2-0455, 1.5-0772, or 1.6-0847 or later. Additionally, implement proper input validation and output encoding for all user-supplied metadata fields.
- Consultation2.0 h
- Implementation8.0 h
- Testing6.0 h
- Review / QA3.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $5,248.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2015-9105 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2015-9105 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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