CVE-2017-12072
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 · uneditedCross-site scripting (XSS) vulnerability in PixlrEditorHandler.php in Synology Photo Station before 6.8.0-3456 allows remote authenticated users to inject arbitrary web scripts or HTML via the id parameter.
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 confidenceA reflected cross-site scripting (XSS) vulnerability exists in the PixlrEditorHandler.php component of Synology Photo Station. The flaw allows authenticated remote users to inject arbitrary JavaScript or HTML through the unsanitized 'id' parameter, potentially enabling session hijacking or phishing attacks against other users viewing the affected page.
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< 6.8.0-3456CVSS 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.0/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 checksWork through these to decide whether this CVE applies to you.
-
Verify Photo Station is installedAccess your Synology DSM, open Package Center, and confirm Photo Station is listed as an installed package. Alternatively, attempt to access the Photo Station web interface at http://[your-nas]/photo/Affected if Photo Station is installed and running
-
Check installed Photo Station versionIn DSM Package Center, select Photo Station and view the version details. Alternatively, log into Photo Station, go to Settings > About, and note the version number displayed.Affected if The installed version is lower than 6.8.0-3456 (for example, 6.7.5-3210 or any 6.x version prior to 6.8.0-3456)
-
Locate vulnerable componentAccess your Synology via SSH or File Station and navigate to the Photo Station web directory (typically /var/packages/PhotoStation/target/ui/ or /web/photox/ depending on version). Look for the file PixlrEditorHandler.phpAffected if The file PixlrEditorHandler.php exists in the Photo Station web directory
-
Confirm parameter exposureWith an authenticated Photo Station session, craft a test URL: http://[your-nas]/photo/PixlrEditorHandler.php?id=<script>alert('test')</script> - If an alert dialog executes or the script tag appears in the page source unescaped, the XSS is present.Affected if The injected script executes or renders unescaped in the response, confirming the 'id' parameter is not sanitized
You are affected if Photo Station is running with a version below 6.8.0-3456 AND the PixlrEditorHandler.php component is accessible to authenticated users.
Generated from the published advisory. Verify against your own configuration.
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 data6.8.0-3456
Upgrade Synology Photo Station to version 6.8.0-3456 or later. As an interim measure, restrict Photo Station access to trusted users only until the upgrade can be applied.
- Consultation2.0 h
- Implementation3.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2017-12072 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2017-12072 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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