Photo StationApplication · Qnap

CVE-2020-2502

MEDIUM · 6.1 CVSS v3.1 Published 2021-02-17
Fix available
A fix is available. Upgrade to 6.0.11 or later.
See remediation →
68/100
Remediation priority · Elevated
Remotely reachable No privileges

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 cross-site scripting vulnerability in Photo Station allows remote attackers to inject malicious code. QANP We have already fixed this vulnerability in the following versions of Photo Station. Photo Station 6.0.11 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 vulnerability in QNAP Photo Station allowing remote attackers to inject malicious JavaScript code through unspecified vectors. The vulnerability is network-exploitable and requires no authentication.

MitigationUpdate Photo Station to version 6.0.11 or later to remediate the vulnerability. Verify application functionality after updating.

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

CVSS:3.1/AV:N/AC:L/PR:N/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 on the QNAP device
    Access the QNAP App Center or QTS desktop and verify that Photo Station application appears in the installed applications list. Alternatively, attempt to access the Photo Station web interface by navigating to http(s)://[NAS_IP]/photo/
    Affected if Photo Station is not listed as an installed application or the Photo Station web interface is not accessible, the system is not affected by this vulnerability.
  2. Identify the installed Photo Station version
    Log into the Photo Station web interface as an administrator. Navigate to the Settings or About section, where the application version is typically displayed. Alternatively, check the QNAP App Center which shows the installed version of Photo Station.
    Affected if The detected version is any version prior to 6.0.11 (for example, 6.0.10, 5.x, or earlier), the system is vulnerable to this XSS flaw.
  3. Verify the Photo Station web interface is network-accessible
    Attempt to reach the Photo Station URL (typically /photo/ or /photo/index.php) from a client on the network. Confirm the service is listening and responding. Check if the QNAP device has port forwarding or firewall rules that allow external access to Photo Station.
    Affected if The Photo Station web interface is exposed to untrusted networks (such as the internet), the XSS vulnerability can be exploited by remote attackers without authentication.
  4. Compare installed version against affected range
    Document the exact Photo Station version number found in step 2 and compare it to the affected range: versions less than 6.0.11 are vulnerable.
    Affected if The installed version is below 6.0.11 and Photo Station is accessible as described above, the environment is affected by CVE-2020-2502.

A system is affected if Photo Station is installed and running with a version lower than 6.0.11, with the web interface accessible to potential attackers.

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.

From vendor data
Upgrade available Upgrade to 6.0.11 or later
Fixed in 6.0.11
Interim mitigation

Update Photo Station to version 6.0.11 or later to remediate the vulnerability. Verify application functionality after updating.

Fix this in Photo Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
6.0 hours of engineering $1,060
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,696.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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