CVE Intelligence
High Injection exploit reference

CVE-2022-50789 — SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Conditional Command Injection via dns.php

SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x contains a command injection vulnerability that allows local authenticated users to create malicious files in the /tmp directory with .dns.pid extension. Unauthenticated attackers can execute the malicious commands by making a single HTTP POST request to the vulnerable dns.php script, which triggers command execution and then deletes the file.

Published Dec 30, 2025 · Updated Oct 13, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP · CNA: VulnCheck

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 4.2% (30-day exploitation probability)+14
  • Technical severity (high)+6
  • CISA SSVC: exploitation "poc"+5

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
4.2%
ahead of 91% of scored CVEs · Oct 14, 2026
Affects
Kantar Media
WM2 and 14 more
CVSS base
7.8
High · 3 source(s)

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
Proof of concept
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

No fix documented by the sources we poll. That does not mean none exists: check the vendor advisory.

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Kantar Media WM2, Sound4 Big Voice2 Firmware, Sound4 Big Voice4 Firmware…).
  2. No fix documented in the sources: reduce exposure and monitor the vendor advisory.
  3. EPSS ahead of 91% of scored CVEs: prioritize it in the patch queue.
  4. Search available logs for exploit probes matching the vulnerability class (injection), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Kantar Media WM2 version 1.11 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 Big Voice2 Firmware version 1.30 Vulnerable NIST National Vulnerability Database
Sound4 Big Voice4 Firmware version 1.2 Vulnerable NIST National Vulnerability Database
Sound4 BigVoice2 version 1.30 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 BigVoice4 version 1.2 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 First Firmware version 2.15version 1.69 Vulnerable NIST National Vulnerability Database
Sound4 Impact Eco Firmware version 1.16 Vulnerable NIST National Vulnerability Database
Sound4 Impact Firmware version 2.15version 1.69 Vulnerable NIST National Vulnerability Database
Sound4 Impact/Pulse Eco version 1.16 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 Impact/Pulse/First version Version 2: 1.1/2.15 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 Pulse Eco Firmware version 1.16 Vulnerable NIST National Vulnerability Database
Sound4 Pulse Firmware version 2.15version 1.69 Vulnerable NIST National Vulnerability Database
Sound4 Stream version 1.1/2.4.29 Vulnerable CVE Program (cve.org) e CISA ADP
Sound4 Stream Extension version 2.4.29 Vulnerable NIST National Vulnerability Database
Sound4 Wm2 Firmware version 1.11 Vulnerable NIST National Vulnerability Database

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Local
Attack complexity
Low
Privileges required
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
8.5 CVSS 4.0 High — — disclosure@vulncheck.com via NIST National Vulnerability Database
8.5 CVSS 4.0 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
7.8 CVSS 3.1 High 1.8 5.9 disclosure@vulncheck.com via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — VulnCheck via CVE Program (cve.org) e CISA ADP
CVSS:3.1/AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H (score shown at the top: disclosure@vulncheck.com)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-78 · OS Command Injection

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 4.20%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Look for parameters with command/query metacharacters and unexpected child processes of the service.
endpoint telemetry (EDR)application logs

Timeline

What happened to this CVE, newest first.

  • 2026
  • Affected products added · sound4 ltd./impact/pulse/first, sound4 ltd./impact/pulse eco, sound4 ltd./bigvoice4, sound4 ltd./bigvoice2, sound4 ltd./
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • CVSS changed · 7.8
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Modified
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Dec 30, 2025 · VulnCheck

Source activity

Repeated readings are counted rather than listed.

  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

5 on the record

Elsewhere on this site

Kantar Media
every CVE for this vendor
Injection
same class
CWE-78
other pages naming this weakness

Related CVEs (same products)

  • Critical CVE-2022-50796 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Unauthenticated Remote Code Execution via upload.cgi Dec 30, 2025
  • High CVE-2022-50795 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Conditional Command Injection via traceroute.php Dec 30, 2025
  • Critical CVE-2022-50794 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Unauthenticated Command Injection via Username Dec 30, 2025
  • High CVE-2022-50793 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Authenticated Command Injection via www-data-handler.php Dec 30, 2025
  • High CVE-2022-50792 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Unauthenticated File Disclosure Vulnerability Dec 30, 2025
  • High CVE-2022-50788 SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Information Disclosure via Log Directory Dec 30, 2025

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No fixed version, patch or mitigation documented.
  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2022-50789 is "SOUND4 IMPACT/FIRST/PULSE/Eco <=2.x Conditional Command Injection via dns.php", rated High. It affects WM2 (Kantar Media); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 7.8 describes technical severity. EPSS 4.20% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.