dbcve.org
Video Management Software ServerApplication · Wavestore

CVE-2025-65075

MEDIUM · 6.5 CVSS v3.1 Published 2025-12-16
Fix available
A fix is available. Upgrade to after 6.42.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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
WaveView client allows users to execute restricted set of predefined commands and scripts on the connected WaveStore Server. A malicious attacker with high-privileges is able to read or delete files, with the permissions of dvr user, on the server using path traversal in the alog script. This issue was fixed in version 6.44.44

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 confidence

Path traversal vulnerability in the alog script of WaveStore Server allows authenticated high-privilege users to read or delete files outside the intended directory by using '../' sequences. The vulnerability stems from insufficient input validation on file paths, and the attack executes with dvr user permissions.

MitigationUpgrade WaveStore Server to version 6.44.44 or later to obtain the patched alog script with proper path validation. Until then, restrict high-privilege access and monitor for suspicious file access patterns.

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
Video Management Software ServerApplication
Affected:<= 6.42.4

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
High
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:H/I:H/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. Identify WaveStore Server version
    Locate and read the WaveStore Server version information, typically found in the software's about panel, installation directory, or by running 'wavestore --version' or 'wavestore -v' from the command line if available
    Affected if The installed version is 6.42.4 or lower (any version up to and including 6.42.4)
  2. Locate the alog script
    Search for the 'alog' script in the WaveStore installation directory, commonly under /opt/wavestore/, /usr/local/wavestore/, or the server's bin/scripts folder. Use 'find / -name alog -type f 2>/dev/null' if filesystem access permits
    Affected if The alog script exists and is present in the WaveStore installation directory
  3. Verify high-privilege user access
    Review user account permissions in the WaveStore admin interface or system user database. Identify accounts with administrative or high-privilege roles that can access the alog functionality
    Affected if There are authenticated users with high-privilege or administrative access to the WaveStore Server
  4. Test for path traversal vulnerability (if authorized)
    If you have legitimate authorization and access, attempt to access a test file outside the intended directory using '../' sequences through the alog script parameter, such as 'alog ../../../etc/passwd' or similar path construction
    Affected if The alog script accepts and processes '../' sequences, allowing access to files outside the intended directory scope

A user is affected if they are running WaveStore Server version 6.42.4 or lower AND have high-privilege users who can access the alog script, which would allow path traversal attacks to read or delete files outside the intended directory with dvr user permissions.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 6.42.4
Interim mitigation

Upgrade WaveStore Server to version 6.44.44 or later to obtain the patched alog script with proper path validation. Until then, restrict high-privilege access and monitor for suspicious file access patterns.

Recommended fix Moderate confidence

Upgrade to WaveStore Server version 6.44.44

  1. 1. Back up the current Video Management Software Server configuration and database
  2. 2. Download WaveStore Server version 6.44.44 from the official vendor website (www.wavestore.com)
  3. 3. Stop the WaveStore Server service
  4. 4. Install version 6.44.4 by running the installer with appropriate privileges
  5. 5. Restart the WaveStore Server service
  6. 6. Verify the installation by checking the version number in the server administration interface
  7. 7. Test that the path traversal vulnerability is no longer exploitable in the alog script functionality
Caveat Review release notes for any configuration or feature changes between your current version and 6.44.44

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Video Management Software Server Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-65075 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2025-65075 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