dbcve.org
Photo StationApplication · Synology

CVE-2017-11161

CRITICAL · 9.8 CVSS v3.0 Published 2017-09-08
Fix available
A fix is available. Upgrade to after 6.7.3-3432 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 SQL injection vulnerabilities in Synology Photo Station before 6.7.4-3433 and 6.3-2968 allow remote attackers to execute arbitrary SQL commands via the (1) article_id parameter to label.php; or (2) type parameter to synotheme.php.

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 SQL injection vulnerabilities in Synology Photo Station allow remote attackers to execute arbitrary SQL commands via the article_id parameter in label.php or the type parameter in synotheme.php. The critical CVSS 9.8 score indicates trivial exploitability from network with no authentication required.

MitigationUpgrade Synology Photo Station to version 6.7.4-3433 or later (6.x branch) or 6.3-2968 or later (6.3 branch) to patch the SQL injection vulnerabilities. If immediate patching is not possible, restrict network access to Photo Station endpoints as a temporary measure.

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-2967<= 6.7.3-3432

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
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/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. Identify Photo Station version
    Access Synology DiskStation Manager (DSM), open Package Center, locate Synology Photo Station, and note the installed version number displayed
    Affected if version is 6.3-2967 or lower, or 6.7.3-3432 or lower
  2. Compare version to affected ranges
    Review the version number from Package Center against the known affected versions: 6.3-2967 and below, or 6.7.3-3432 and below
    Affected if installed version falls within or below these ranges
  3. Check network exposure of Photo Station
    Determine if the Synology NAS Photo Station web interface is accessible from external networks or the internet by reviewing firewall rules, router port forwarding, or QuickConnect/DDNS settings
    Affected if Photo Station is exposed to untrusted networks (exploitation requires no authentication)
  4. Verify vulnerable endpoints exist
    Attempt to access the URL paths /photo/label.php and /photo/synotheme.php on the Photo Station server to confirm the application endpoints are present
    Affected if these PHP endpoints return valid responses (indicating they are accessible for potential injection)

A user is affected if Photo Station version is 6.3-2967 or below OR 6.7.3-3432 or below AND the application is network-accessible.

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 a release after 6.7.3-3432
Interim mitigation

Upgrade Synology Photo Station to version 6.7.4-3433 or later (6.x branch) or 6.3-2968 or later (6.3 branch) to patch the SQL injection vulnerabilities. If immediate patching is not possible, restrict network access to Photo Station endpoints as a temporary measure.

Recommended fix High confidence

Photo Station 6.7.4-3433 or higher (6.7.x branch); Photo Station 6.3-2968 or higher (6.3 branch)

  1. 1. Log in to Synology DiskStation Manager (DSM) as administrator
  2. 2. Open Package Center
  3. 3. Locate Photo Station in the installed package list
  4. 4. Click on Photo Station and select 'Update' to install the latest available version
  5. 5. Alternatively, enable automatic updates for Photo Station in Package Center settings
  6. 6. Verify the updated version is 6.7.4-3433 or higher (for DSM 6.7.x) or 6.3-2968 or higher (for DSM 6.3)
Caveat Standard Synology package update - minimal risk; ensure backup of Photo Station data before updating as a precautionary measure

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

Fix this in Photo Station Scoped from the published advisory
  • Consultation3.0 h
  • Implementation4.0 h
  • Testing4.0 h
  • Review / QA2.0 h
13.0 hours of engineering $2,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 $3,648.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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