dbcve.org
Photo StationApplication · Synology

CVE-2019-11821

CRITICAL · 9.8 CVSS v3.1 Published 2019-06-30
Fix available
A fix is available. Upgrade to 6.3-2977 / 6.8.11-3489 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
SQL injection vulnerability in synophoto_csPhotoDB.php in Synology Photo Station before 6.8.11-3489 and before 6.3-2977 allows remote attackers to execute arbitrary SQL command via the type parameter.

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

SQL injection vulnerability in Synology Photo Station's synophoto_csPhotoDB.php allows remote attackers to execute arbitrary SQL commands via the unsanitized 'type' parameter. This is a classic SQL injection flaw where user-supplied input is directly incorporated into database queries without proper parameterization or sanitization.

MitigationUpgrade Photo Station to version 6.8.11-3489 (or 6.3-2977 and later) to patch the vulnerability. If immediate patching is not feasible, implement network-level access controls to limit exposure to untrusted networks.

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, < 6.3-2977>= 6.8, < 6.8.11-3489

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.1/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. Confirm Photo Station installation
    Log into Synology DSM, open Package Center, and look for Photo Station in the installed package list. Alternatively, check the file system for /var/packages/PhotoStation or similar package directories.
    Affected if Photo Station is not installed in the package center or package directory does not exist - not affected.
  2. Identify installed Photo Station version
    In DSM Package Center, click on Photo Station and view the version information. Or check the version via command line if package metadata is accessible in /var/packages/PhotoStation/INFO.
    Affected if Version is within 6.3 through 6.3-2976 (exclusive of 6.3-2977) OR within 6.8 through 6.8-11-3488 (exclusive of 6.8.11-3489) - affected.
  3. Verify vulnerable endpoint is accessible
    Attempt to access the Photo Station web interface at /photo/synophoto_csPhotoDB.php via HTTP/HTTPS. The vulnerability exists in this PHP file when the 'type' parameter is supplied.
    Affected if The web interface is reachable and the synophoto_csPhotoDB.php endpoint responds - vulnerable code path is present.
  4. Confirm Photo Station is enabled and running
    In DSM Control Panel, check Application Portal or Web Services settings to confirm Photo Station is enabled. Verify the web station service is running.
    Affected if Photo Station is enabled and the web service is active - the injection point is exposed to network requests.

User is affected if Photo Station is installed, running, and the version falls within 6.3 to 6.3-2976 or 6.8 to 6.8-3488, with the web interface 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 6.3-2977 / 6.8.11-3489 or later
Fixed in 6.3-29776.8.11-3489
Interim mitigation

Upgrade Photo Station to version 6.8.11-3489 (or 6.3-2977 and later) to patch the vulnerability. If immediate patching is not feasible, implement network-level access controls to limit exposure to untrusted networks.

Recommended fix High confidence

Photo Station 6.3-2977 or 6.8.11-3489 (depending on current branch)

  1. 1. Identify the current installed version of Synology Photo Station in the Package Center
  2. 2. Back up all Photo Station data and configurations as a precautionary measure
  3. 3. Open Package Center and locate Photo Station
  4. 4. Update Photo Station to version 6.3-2977 or later (if on 6.3.x branch), or version 6.8.11-3489 or later (if on 6.8.x branch)
  5. 5. Verify the update was successful and the application functions normally

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

Fix this in Photo Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
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,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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