dbcve.org
Stream ExtensionPlugin / extension · Sound4

CVE-2023-53955

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-22
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges 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
SOUND4 IMPACT/FIRST/PULSE/Eco v2.x contains an insecure direct object reference vulnerability that allows attackers to bypass authorization and access hidden system resources. Attackers can exploit the vulnerability by manipulating user-supplied input to execute privileged functionalities without proper authentication.

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

SOUND4 IMPACT/FIRST/PULSE/Eco v2.x broadcast audio processors contain an Insecure Direct Object Reference (IDOR) vulnerability that allows unauthenticated attackers to bypass authorization checks by manipulating user-supplied input, enabling access to hidden system resources and privileged functionalities.

MitigationImplement proper authorization validation on all object references and enforce authentication checks for privileged operations. Consider updating to a patched version if available from the vendor.

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
Stream ExtensionPlugin / extension
Affected:= 2.4.29
Wm2 FirmwareOperating system
Affected:= 1.11
Big Voice2 FirmwareOperating system
Affected:= 1.30
Big Voice4 FirmwareOperating system
Affected:= 1.2
Pulse Eco FirmwareOperating system
Affected:= 1.16
Impact Eco FirmwareOperating system
Affected:= 1.16
First FirmwareOperating system
Affected:= 1.69= 2.15
Pulse FirmwareOperating system
Affected:= 1.69= 2.15

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

CVSS:3.1/AV:N/AC:L/PR:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the Sound4 product in use
    Access the web management interface of the device or check the device labeling/documentation to determine if it is a Sound4 IMPACT, FIRST, PULSE, Eco, Stream Extension, Wm2, Big Voice2, or Big Voice4 model.
    Affected if The device is any of the Sound4 models listed in the affected products.
  2. Determine the firmware or software version
    Log into the Sound4 web interface and navigate to System Info, About, or Settings section to find the firmware version. For Stream Extension, check the software version in the application.
    Affected if The installed version cannot be determined or is not visible in the standard interface.
  3. Compare installed version against affected versions
    Match the identified firmware version to the following affected list: Stream Extension = 2.4.29; Wm2 = 1.11; Big Voice2 = 1.30; Big Voice4 = 1.2; Pulse Eco = 1.16; Impact Eco = 1.16; First = 1.69 or 2.15; Pulse = 1.69 or 2.15.
    Affected if The installed version exactly matches any version listed in the affected products.
  4. Verify web interface accessibility
    Confirm that the Sound4 web management interface is accessible from the network. Attempt to access common paths such as /, /admin, or /webui.
    Affected if The web interface is exposed and reachable from untrusted networks.
  5. Check for unauthenticated endpoint access
    Attempt to access URL parameters or endpoints that may reference internal objects, such as configuration files, user IDs, or system resources, without providing valid authentication credentials.
    Affected if Hidden system resources or privileged functionalities are accessible without proper authorization.

The environment is affected if a Sound4 product is running and its firmware version exactly matches one of the listed affected versions, with the web interface exposed to network access.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Implement proper authorization validation on all object references and enforce authentication checks for privileged operations. Consider updating to a patched version if available from the vendor.

Fix this in Stream Extension Scoped from the published advisory
  • Consultation8.0 h
  • Implementation16.0 h
  • Testing12.0 h
  • Review / QA8.0 h
44.0 hours of engineering $7,720
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2023-53955 — 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-2023-53955 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