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

CVE-2022-27593

CRITICAL · 9.1 CVSS v3.1 Published 2022-09-08
Fix available
A fix is available. Upgrade to 5.2.14 / 5.4.15 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Ransomware High EPSS 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
An externally controlled reference to a resource vulnerability has been reported to affect QNAP NAS running Photo Station. If exploited, This could allow an attacker to modify system files. We have already fixed the vulnerability in the following versions: QTS 5.0.1: Photo Station 6.1.2 and later QTS 5.0.0/4.5.x: Photo Station 6.0.22 and later QTS 4.3.6: Photo Station 5.7.18 and later QTS 4.3.3: Photo Station 5.4.15 and later QTS 4.2.6: Photo Station 5.2.14 and later

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

This is an externally controlled reference to a resource vulnerability in QNAP Photo Station where user-supplied input is used to reference files or resources without proper validation, allowing authenticated attackers to modify arbitrary system files. The CVSS 9.1 score reflects the critical severity of unauthorized system file modification on network-accessible NAS devices.

MitigationUpgrade Photo Station to the fixed version corresponding to your QTS release (6.1.2 for QTS 5.0.1, 6.0.22 for QTS 5.0.0/4.5.x, 5.7.18 for QTS 4.3.6, 5.4.15 for QTS 4.3.3, or 5.2.14 for QTS 4.2.6). If patching is not immediately feasible, restrict access to the Photo Station interface via firewall rules or disable the application until the update can be applied.

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:< 5.2.14< 5.4.15< 5.7.18< 6.0.22< 6.1.2

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

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/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 is installed and running
    Log into the QNAP NAS web interface (QTS) and navigate to App Center or Control Panel > Applications > Photo Station. Verify the Photo Station application is installed and its status shows as running.
    Affected if Photo Station is not installed or not running, the vulnerability does not apply.
  2. Identify the QTS firmware version
    In the QTS web interface, go to Control Panel > System > Firm Update or click the user icon to view system information. Note the QTS version number displayed.
    Affected if The QTS version determines which Photo Station version branch is relevant for vulnerability checking.
  3. Locate the installed Photo Station version
    In QTS App Center, find Photo Station in the installed applications list. The version number is displayed alongside the application name. Alternatively, access Photo Station directly via its web URL (typically /photo/) and check the version in the application settings or about section.
    Affected if The installed version number is needed to compare against the affected ranges.
  4. Compare version against affected ranges
    If running QTS 4.2.6, check if Photo Station version is less than 5.2.14. If QTS 4.3.3, check for version < 5.4.15. If QTS 4.3.6, check for version < 5.7.18. If QTS 4.5.x or 5.0.0, check for version < 6.0.22. If QTS 5.0.1, check for version < 6.1.2.
    Affected if The NAS is vulnerable if the installed Photo Station version falls below the threshold corresponding to the QTS version in use.
  5. Verify Photo Station web access is enabled
    In QTS, go to Control Panel > Applications > Photo Station or Privilege > Applications > Photo Station. Confirm that web access to Photo Station is enabled and the service is exposed via HTTP/HTTPS.
    Affected if The vulnerability requires authenticated access to Photo Station; if remote access is disabled and the attacker cannot reach the service, exploitation is not possible.

The environment is affected if Photo Station is installed, running, web-accessible, and the installed version is lower than the fixed version threshold corresponding to the QTS firmware version in use.

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.14 / 5.4.15 / 5.7.18 or later
Fixed in 5.2.145.4.155.7.18
Interim mitigation

Upgrade Photo Station to the fixed version corresponding to your QTS release (6.1.2 for QTS 5.0.1, 6.0.22 for QTS 5.0.0/4.5.x, 5.7.18 for QTS 4.3.6, 5.4.15 for QTS 4.3.3, or 5.2.14 for QTS 4.2.6). If patching is not immediately feasible, restrict access to the Photo Station interface via firewall rules or disable the application until the update can be applied.

Recommended fix High confidence

Photo Station 6.1.2 (QTS 5.0.1), 6.0.22 (QTS 5.0.0/4.5.x), 5.7.18 (QTS 4.3.6), 5.4.15 (QTS 4.3.3), or 5.2.14 (QTS 4.2.6) - select based on your current QTS version

  1. 1. Identify the QNAP QTS firmware version running on the NAS (check Control Panel > System > Firmware Update)
  2. 2. Determine the current Photo Station version installed (check App Center > Photo Station > Info)
  3. 3. Based on your QTS version, upgrade Photo Station to the minimum fixed version: For QTS 5.0.1 upgrade to Photo Station 6.1.2 or later; For QTS 5.0.0/4.5.x upgrade to Photo Station 6.0.22 or later; For QTS 4.3.6 upgrade to Photo Station 5.7.18 or later; For QTS 4.3.3 upgrade to Photo Station 5.4.15 or later; For QTS 4.2.6 upgrade to Photo Station 5.2.14 or later
  4. 4. Open App Center, locate Photo Station, click Update, and install the available update
  5. 5. After update, verify the Photo Station version matches or exceeds the required fixed version for your QTS release
  6. 6. Confirm Photo Station is functioning normally and review any logs for errors
Caveat Upgrade within same major version typically has low risk; ensure backup of Photo Station data before updating

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
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,190
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,904.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-27593 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2022-27593 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