dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 22 Jun 2022. Known ransomware use
Photo StationApplication · Qnap

CVE-2019-7194

CRITICAL · 9.8 CVSS v3.1 Published 2019-12-05
Fix available
A fix is available. Upgrade to 5.2.11 / 5.4.9 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS Public exploit 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
This external control of file name or path vulnerability allows remote attackers to access or modify system files. To fix the vulnerability, QNAP recommend updating Photo Station to their latest versions.

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 · moderate confidence

A path traversal vulnerability in QNAP Photo Station allows remote attackers to manipulate file paths through user-supplied input, enabling unauthorized access or modification of system files outside the intended web root directory.

MitigationUpdate Photo Station to the latest version available from QNAP to remediate this vulnerability.

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.0.3< 5.7.10< 5.4.9< 5.2.11

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. Verify Photo Station is installed
    Log into QNAP QTS admin panel and navigate to Control Panel > Application > Photo Station, or check if the Photo Station service is running via the QNAP interface.
    Affected if Photo Station is not installed or not in use, the vulnerability does not apply.
  2. Check installed Photo Station version
    In QTS, go to App Center > My Apps > Photo Station and note the version number displayed. Alternatively, access Photo Station directly via its web interface and check the version in the application settings or footer.
    Affected if The installed version is below 6.0.3, 5.7.10, 5.4.9, or 5.2.11 (specifically any version < 6.0.3, or between 5.4.9-5.7.9, or between 5.2.11-5.4.8, or between 5.0.0-5.2.10).
  3. Determine if Photo Station web interface is network-accessible
    Check your router or QNAP firewall settings to confirm whether the Photo Station web port (typically 8080 or 8443 for HTTPS) is forwarded or exposed to external networks. Verify the QNAP myQNAPcloud service status if enabled.
    Affected if The Photo Station web interface is accessible from the internet or untrusted networks, making the path traversal exploitable by remote attackers.
  4. Confirm Photo Station is enabled and running
    In QTS, check Control Panel > System > Services > Photo Station to ensure the service status is Running. Also verify the web server for Photo Station is active.
    Affected if Photo Station is disabled or stopped, the vulnerable code path is not active and cannot be exploited.

A user is affected if Photo Station is installed, running, network-accessible, and the installed version falls within the affected ranges (any version < 6.0.3).

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 5.2.11 / 5.4.9 / 5.7.10 or later
Fixed in 5.2.115.4.95.7.10
Interim mitigation

Update Photo Station to the latest version available from QNAP to remediate this vulnerability.

Recommended fix High confidence

Photo Station 6.0.3 (or latest available version in your branch: 5.7.10, 5.4.9, or 5.2.11)

  1. Log in to QNAP NAS as administrator
  2. Open App Center or the Photo Station application
  3. Check current Photo Station version in the application settings
  4. Navigate to the QNAP download center or App Center to obtain the latest Photo Station version
  5. Install the updated Photo Station version (6.0.3 for v6.x, 5.7.10 for v5.7.x, 5.4.9 for v5.4.x, or 5.2.11 for v5.2.x)
  6. Restart the Photo Station service after update completion
  7. Verify the new version is installed successfully

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

Fix this in Photo Station Exploited in the wild — priority engagement
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get it fixed fast

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-2019-7194 — 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-7194 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