Photo StationApplication · Qnap

CVE-2018-19955

MEDIUM · 6.1 CVSS v3.1 Published 2020-11-02
Fix available
A fix is available. Upgrade to 5.7.11 / 6.0.10 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
The cross-site scripting vulnerability has been reported to affect earlier versions of Photo Station. If exploited, the vulnerability could allow remote attackers to inject malicious code. This issue affects: QNAP Systems Inc. Photo Station versions prior to 5.7.11; versions prior to 6.0.10.

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

A cross-site scripting (XSS) vulnerability in QNAP Photo Station allows remote attackers to inject malicious code through user-supplied input that is rendered without proper sanitization. This is a stored XSS vulnerability affecting versions prior to 5.7.11 and 6.0.10.

MitigationUpgrade Photo Station to version 5.7.11 or later, or version 6.0.10 or later, to remediate the 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:>= 5.7.0, < 5.7.11>= 6.0.0, < 6.0.10

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. Locate Photo Station version in QNAP admin interface
    Log into the QNAP admin console, navigate to the Photo Station application, and find the version information typically displayed in the application settings or 'About' section. Alternatively, use the QNAP App Center to view installed application versions.
    Affected if The installed version is 5.7.0 through 5.7.10, or 6.0.0 through 6.0.9 (any version prior to 5.7.11 or 6.0.10).
  2. Identify the Photo Station version via QNAP command line
    If you have SSH access to the QNAP device, check the installed Photo Station package version using the command 'qpkg -g PhotoStation' or by listing installed apps with 'qpkg --list | grep -i photo'.
    Affected if The returned version number falls within the affected ranges 5.7.0-5.7.10 or 6.0.0-6.0.9.
  3. Confirm the Photo Station installation is exposed to remote access
    Verify that Photo Station is accessible over the network (myqnapcloud.com or local network access) and that the web interface is enabled. Check the QNAP Control Panel > Applications > Photo Station to confirm the service is running and accessible.
    Affected if Photo Station is enabled and accessible remotely; the XSS can be exploited through user-supplied input submitted to the application.
  4. Review application logs for suspicious input patterns
    Check Photo Station logs (accessible via the QNAP admin interface under Log Center or in /var/log/PhotoStation/) for any evidence of malicious script tags or unusual input patterns in user-contributed fields.
    Affected if Unusual script tags appear in log entries, indicating potential exploitation attempts or successful XSS injection.

You are affected if Photo Station is running version 5.7.0 through 5.7.10 or version 6.0.0 through 6.0.9, as these versions contain the vulnerable code that fails to sanitize user-supplied input.

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 5.7.11 / 6.0.10 or later
Fixed in 5.7.116.0.10
Interim mitigation

Upgrade Photo Station to version 5.7.11 or later, or version 6.0.10 or later, to remediate the vulnerability.

Fix this in Photo Station Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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