dbcve.org
Photo StationApplication · Qnap

CVE-2023-47562

HIGH · 8.8 CVSS v3.1 Published 2024-02-02
Fix available
A fix is available. Upgrade to 6.4.2 or later.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 OS command injection vulnerability has been reported to affect Photo Station. If exploited, the vulnerability could allow authenticated users to execute commands via a network. We have already fixed the vulnerability in the following version: Photo Station 6.4.2 ( 2023/12/15 ) 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

OS command injection vulnerability in QNAP Photo Station allows authenticated users to execute arbitrary operating system commands via network requests. The vulnerability stems from insufficient input validation in the Photo Station web application interface.

MitigationUpdate Photo Station to version 6.4.2 or later to remediate the command injection vulnerability. Apply the update following QNAP's standard upgrade procedures and verify functionality post-update.

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.4.0, < 6.4.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
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/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 is installed
    Access the QNAP admin interface and navigate to the application list, or check for Photo Station in the QNAP App Center.
    Affected if Photo Station is not installed on the QNAP device
  2. Identify Photo Station version
    In the QNAP App Center, click on Photo Station and view the version information displayed, or access Photo Station settings and check the About section.
    Affected if Unable to determine the installed version from the interface
  3. Compare version to affected range
    If the installed version is 6.4.0 or 6.4.1, the system falls within the vulnerable range. Versions below 6.4.0 are not affected. Version 6.4.2 and later include the fix.
    Affected if Installed version is 6.4.0 or 6.4.1 (falls within >= 6.4.0 and < 6.4.2)
  4. Verify web interface accessibility
    Attempt to access the Photo Station web portal via browser at https://[QNAP-IP]/photo/ to confirm the application is reachable over the network.
    Affected if Photo Station web interface is accessible and version is 6.4.0 or 6.4.1

The environment is affected if Photo Station is installed with version 6.4.0 or 6.4.1, as these versions fall within the vulnerable range >= 6.4.0 and < 6.4.2 and the web interface 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 6.4.2 or later
Fixed in 6.4.2
Interim mitigation

Update Photo Station to version 6.4.2 or later to remediate the command injection vulnerability. Apply the update following QNAP's standard upgrade procedures and verify functionality post-update.

Recommended fix High confidence

Photo Station 6.4.2

  1. Log into the QNAP NAS administration interface
  2. Navigate to the Photo Station application
  3. Check the current version to confirm it is between 6.4.0 and 6.4.1 (inclusive)
  4. Back up Photo Station data and configurations as a precautionary measure
  5. Download Photo Station version 6.4.2 or later from the QNAP download center or update via App Center
  6. Install or update Photo Station to version 6.4.2
  7. Verify the installation was successful and confirm the new version number

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

Fix this in Photo Station Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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