CVE-2022-50694
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 · uneditedSOUND4 IMPACT/FIRST/PULSE/Eco <=2.x contains an SQL injection vulnerability in the 'username' POST parameter of index.php that allows attackers to manipulate database queries. Attackers can inject arbitrary SQL code through the username parameter to bypass authentication and potentially access unauthorized database information.
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 · high confidenceSQL injection vulnerability in the authentication login form (index.php) of SOUND4 audio processing devices. The 'username' POST parameter is not properly sanitized before being used in SQL queries, allowing attackers to inject arbitrary SQL code to bypass authentication or exfiltrate database contents.
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= 2.15= 1.69= 2.15= 1.69= 2.15= 1.69= 1.16= 1.16= 1.2= 1.30= 1.11CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Sound4 device modelAccess the device web interface or check device documentation/labels to confirm it is a Sound4 audio processing device (Impact, Pulse, First, Impact Eco, Pulse Eco, Big Voice4, Big Voice2, or Wm2)Affected if The device is any of these Sound4 models
-
Check firmware versionLog into the device web interface or access the admin/system information page to view the installed firmware versionAffected if The firmware version is 2.15, 1.69, 1.16, 1.2, 1.30, or 1.11 for the respective model listed in the affected products
-
Verify web interface is accessibleAttempt to access the device login page at index.php over the network (http/https)Affected if The web interface login form is reachable over the network
-
Confirm username POST parameter existsInspect the login form HTML source or capture a POST request to index.php during login to verify the 'username' parameter is presentAffected if The login form submits a 'username' parameter via POST to index.php
-
Check if remote authentication is enabledDetermine whether the device allows remote network access to the web authentication interface (check network settings or firewall rules)Affected if Remote access to the web login form is permitted on the network
The environment is affected if it is a Sound4 device (Impact, Pulse, First, Impact Eco, Pulse Eco, Big Voice4, Big Voice2, or Wm2) running the specific vulnerable firmware versions (2.15, 1.69, 1.16, 1.2, 1.30, or 1.11) and the web interface with the login form is accessible.
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 dataReplace dynamic SQL query construction with parameterized queries (prepared statements) in the authentication code. Implement strict input validation as an additional layer of defense.
- 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-2022-50694 — 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-2022-50694 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