CVE-2021-29090
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 · uneditedImproper neutralization of special elements used in an SQL command ('SQL Injection') vulnerability in PHP component in Synology Photo Station before 6.8.14-3500 allows remote authenticated users to execute arbitrary SQL command via unspecified vectors.
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 confidenceSQL injection vulnerability in the PHP component of Synology Photo Station allows remote authenticated users to execute arbitrary SQL commands through unspecified vectors. The vulnerability exists in versions prior to 6.8.14-3500 and enables attackers to manipulate database queries, potentially exposing or modifying sensitive data.
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, < 6.8.14-3500CVSS 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
- High
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:H/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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Photo Station is installedLog into Synology DSM and navigate to Package Center to verify Photo Station package is installed, or run 'grep -i photo /var/packages.json' to list installed packagesAffected if Photo Station package is present on the system
-
Identify installed Photo Station versionIn DSM Package Center, click on Photo Station and view the version information, or check via command line using 'cat /var/packages/PhotoStation/info'Affected if Version cannot be determined or is empty
-
Compare version against affected rangeCompare your installed version to the affected range: versions 6.8 through versions prior to 6.8.14-3500 are vulnerableAffected if Installed version is 6.8.x or falls between 6.8 and 6.8.14-3500 (exclusive)
-
Verify remote authenticated access configurationCheck Photo Station settings in DSM: go to Photo Station > Settings > Security and review authentication and access permissions, or inspect /usr/syno/etc/www/PhotoStation/config.php for authentication settingsAffected if Remote authenticated user access to Photo Station is enabled
The environment is affected if Photo Station is installed with a version between 6.8 and 6.8.14-3500 and remote authenticated users can access the Photo Station interface.
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.14-3500
Update Synology Photo Station to version 6.8.14-3500 or later. If immediate patching is not feasible, restrict network access to the Photo Station interface to trusted users only and monitor for unusual database activity.
- Consultation2.0 h
- Implementation1.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,224.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-29090 — 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-2021-29090 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