CVE-2023-50360
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 · uneditedA SQL injection vulnerability has been reported to affect Video Station. If exploited, the vulnerability could allow authenticated users to inject malicious code via a network. We have already fixed the vulnerability in the following version: Video Station 5.8.1 ( 2024/02/26 ) 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 confidenceSQL injection vulnerability in Synology Video Station allowing authenticated users to inject malicious SQL code through network requests. The vulnerability stems from improper input sanitization in database queries, enabling attackers to manipulate SQL statements.
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>= 5.0.0, < 5.8.2CVSS 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
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:L/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 Video Station installationLocate the Qnap Video Station application on the system. Check for the presence of the Video Station package through the Qnap App Center or by searching for video station related files in the system (commonly under /share/CACHEDEV1_DATA/.qpkg/VideoStation or similar paths).Affected if Video Station is installed and running on the Qnap system
-
Determine installed Video Station versionAccess the Qnap admin interface, navigate to App Center, find Video Station, and note the version number displayed. Alternatively, check the version file within the Video Station package directory if shell access is available.Affected if The installed version is 5.0.0 or higher but lower than 5.8.2
-
Verify authenticated user access to Video StationCheck if any user accounts have access to Video Station functionality. Review the user privileges in Qnap NAS settings under Access Control > Share Folders or Video Station settings to confirm authenticated users can use the application.Affected if Authenticated users exist with access to Video Station and can make network requests to the application
-
Inspect network request parametersIf you have access to Video Station logs or can monitor network traffic, examine requests to the Video Station API endpoints (typically under /videoStation/api or similar). Look for database query parameters that accept user input without apparent sanitization.Affected if The application processes SQL-like queries through network endpoints accessible to authenticated users
The environment is affected if Qnap Video Station version 5.0.0 through 5.8.1 is installed and authenticated users can access the application's network-facing query functionality.
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.
dbcve · scoped5.8.2
Update Video Station to version 5.8.1 or later. Additionally, review and enforce least-privilege access controls for authenticated users and implement parameterized queries across the codebase.
Video Station 5.8.1 or later
- Upgrade Video Station to version 5.8.1 or later
- After upgrading, verify the version number in the QNAP admin interface to confirm the patch was applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-50360 — 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-2023-50360 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