dbcve.org
Photo StationApplication · Synology

CVE-2015-9102

MEDIUM · 5.4 CVSS v3.0 Published 2017-06-30
Fix available
A fix is available. Upgrade to after 6.3-2960 or later.
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
Multiple cross-site scripting (XSS) vulnerabilities in Synology Photo Station 6.0 before 6.0-2638 and 6.3 before 6.3-2962 allow remote authenticated attackers to inject arbitrary web script or HTML via the (1) album name, (2) file name of uploaded photos, (3) description of photos, or (4) tag of the photos.

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

Multiple stored cross-site scripting (XSS) vulnerabilities exist in Synology Photo Station versions 6.0 before 6.0-2638 and 6.3 before 6.3-2962. Authenticated attackers can inject malicious JavaScript or HTML through four input fields: album names, uploaded photo filenames, photo descriptions, and photo tags. The injected scripts execute in the browsers of other users viewing the affected content.

MitigationUpdate Photo Station to version 6.0-2638 or 6.3-2962 or later. Until patched, restrict Photo Station access to trusted users only and implement Content Security Policy headers to mitigate XSS 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
Photo StationApplication
Affected:<= 6.3-2960

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. Identify Photo Station version
    Access Synology DSM > Package Center > Photo Station and note the installed version number displayed in the package details panel
    Affected if version is 6.3-2960 or lower, or any 6.0 version before 6.0-2638
  2. Compare version to affected ranges
    Check if installed version falls within: 6.0 through 6.0-2637, or 6.3 through 6.3-2960. Versions 6.0-2638+ and 6.3-2962+ are patched
    Affected if installed version is within the vulnerable ranges and has not been updated
  3. Verify Photo Station access controls
    In DSM, go to Control Panel > Shared Folder > Photo Station permissions and confirm which user groups have access to Photo Station. Check if guest access or untrusted user accounts are enabled
    Affected if Photo Station is accessible to guest users or untrusted/non-administrator accounts
  4. Inspect album names for injected content
    In Photo Station web interface, navigate through albums and manually inspect album names for unusual characters or script tags. Alternatively, query the PhotoStation database (SQLite: photo.db) in /volumeX/@appstore/PhotoStation/ for entries containing script or iframe tags in album_name fields
    Affected if any album names contain HTML script tags, iframe elements, or javascript: URIs
  5. Inspect photo metadata fields for XSS payloads
    Browse Photo Station photo library and check photo descriptions and tags visible in photo detail views. In the database, examine photo and tag tables for entries containing <script>, <img onerror>, or javascript: prefixes
    Affected if photo descriptions, filenames, or tags contain executable JavaScript or HTML tags

The environment is affected if Photo Station version is 6.3-2960 or lower (or 6.0 before 6.0-2638) AND the application is accessible to users who could inject malicious content, or if the database already contains XSS payloads in albums, photos, or tags.

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
Upgrade available Upgrade to a release after 6.3-2960
Interim mitigation

Update Photo Station to version 6.0-2638 or 6.3-2962 or later. Until patched, restrict Photo Station access to trusted users only and implement Content Security Policy headers to mitigate XSS execution.

Fix this in Photo Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,920
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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