Photo StationApplication · Qnap

CVE-2024-12923

MEDIUM · 5.4 CVSS v3.1 Published 2025-08-29
Fix available
A fix is available. Upgrade to 6.4.5 or later.
See remediation →
58/100
Remediation priority · Elevated
Remotely reachable

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
A cross-site scripting (XSS) vulnerability has been reported to affect Photo Station. If a remote attacker gains a user account, they can then exploit the vulnerability to bypass security mechanisms or read application data. We have already fixed the vulnerability in the following version: Photo Station 6.4.5 ( 2025/01/02 ) 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 · moderate confidence

Cross-site scripting (XSS) vulnerability in QNAP Photo Station. Attackers with a valid user account can exploit the XSS to bypass security mechanisms or access application data. The CVSS 5.4 indicates network-exploitable XSS requiring user authentication.

MitigationUpgrade Photo Station to version 6.4.5 or later. Since the vulnerability requires a user account, ensure strong credential policies and consider implementing additional input validation as a defense-in-depth 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.4.0, < 6.4.5

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
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N

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
    Log into the QNAP device web interface and check if Photo Station is available, or use the QNAP App Center to list installed applications. Photo Station may also appear in the main menu or desktop of the QTS interface.
    Affected if Photo Station is not installed - the vulnerability does not apply
  2. Locate the Photo Station version
    Access the Photo Station web application and navigate to the About or Settings page where version information is displayed. Alternatively, open QNAP App Center, right-click on Photo Station, and select 'Information' to view the version.
    Affected if Unable to locate version information - cannot determine exposure
  3. Compare installed version to affected range
    Note the exact version number displayed (format is 6.x.x). Compare it against the vulnerable range: version 6.4.0 through 6.4.4 are affected. Versions below 6.4.0 or at/above 6.4.5 are not vulnerable.
    Affected if Installed version is 6.4.0, 6.4.1, 6.4.2, 6.4.3, or 6.4.4 - the environment is affected by this XSS vulnerability

The environment is affected only if Photo Station is installed and the running version falls within 6.4.0 to 6.4.4 inclusive.

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.5 or later
Fixed in 6.4.5
Interim mitigation

Upgrade Photo Station to version 6.4.5 or later. Since the vulnerability requires a user account, ensure strong credential policies and consider implementing additional input validation as a defense-in-depth measure.

Recommended fix High confidence

Photo Station 6.4.5

  1. Check the current version of Photo Station installed on the QNAP NAS by navigating to App Center > Photo Station > Open
  2. If the installed version is below 6.4.5, update Photo Station to version 6.4.5 or later through the QNAP App Center
  3. After updating, verify the new version is 6.4.5 or higher to confirm the vulnerability is patched

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
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
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,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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