CVE-2023-34977
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 cross-site scripting (XSS) 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.7.0 ( 2023/07/27 ) 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 confidenceThis is a stored cross-site scripting (XSS) vulnerability in QNAP Video Station. Authenticated users can inject malicious JavaScript code through input fields that gets stored and executed when other users view the affected content. The vulnerability is exploitable over the network and requires user authentication.
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< 2023.07.27CVSS 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.1/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 Video Station is installedAccess QNAP NAS admin interface and check installed apps, or use QCLI command line tool if availableAffected if Video Station application is present on the NAS
-
Check Video Station versionNavigate to Video Station Settings > About, or check the QNAP App Center for the installed version numberAffected if Version is earlier than 5.7.0 or shows a date before 2023/07/27
-
Confirm authentication is enabledVerify that Video Station user authentication is configured and functional - check that login is required to access the applicationAffected if User authentication is not required or is bypassed (less likely but increases exposure)
-
Identify active input fieldsCheck if Video Station allows user-generated content through fields such as video titles, descriptions, or metadata that could store malicious scriptsAffected if User-contributed content fields exist and are accessible to authenticated users
If Video Station is installed and the version is earlier than 5.7.0 (or dated before 2023-07-27), the environment is vulnerable to stored XSS via authenticated user input fields.
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 · scoped2023.07.27
Update Video Station to version 5.7.0 (released 2023/07/27) or later. Until patched, limit access to trusted authenticated users and monitor for suspicious activity.
Video Station 5.7.0 (2023/07/27) or later
- 1. Check current Video Station version in QNAP App Center or Video Station settings
- 2. Backup any critical Video Station data and configurations as a precautionary measure
- 3. Update Video Station to version 5.7.0 or later (released 2023/07/27) via QNAP App Center
- 4. Verify the installed version after update to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,088.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2023-34977 — 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-34977 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