Web
CVE-2022-50789
Unauthenticated web command injection in dns.php enables RCE.
- CVSS
- 8.5Highscored by the publisher (CNA)
- Exploited in the wild
- Not knownpublic proof of concept per CISA SSVC; not in CISA KEV
- EPSS
- 4.2%chance of exploitation in the next 30 daystop 9% of scored CVEsFIRST score of 13 Nov 2026
- Fix
- Not stated by the vendorno fixed release in the CVE record
- Published
- 30 Dec 2025analysed here 31 Dec 2025
Summary
Impact
Remote RCE via HTTP POST; arbitrary commands and /tmp file operations possible.
Triage
The summary, impact and action text on this page are written by our AI analysis pipeline, or taken from the NVD description when a CVE was imported from NVD. They are not the vendor's wording: check them against the sources. A longer AI executive summary and technical analysis are generated for signed-in accounts on the Max plan.
Affected products
| Product | Affected versions | Vendor says fixed in |
|---|---|---|
| SOUND4 Ltd. BigVoice2 | 1.30Vendor says fixed in: not stated | |
| SOUND4 Ltd. BigVoice4 | 1.2Vendor says fixed in: not stated | |
| SOUND4 Ltd. Impact/Pulse Eco | 1.16Vendor says fixed in: not stated | |
| SOUND4 Ltd. Impact/Pulse/First | Version 2: 1.1/2.15Vendor says fixed in: not stated | |
| SOUND4 Ltd. Stream | 1.1/2.4.29Vendor says fixed in: not stated | |
| Kantar Media WM2 | 1.11Vendor says fixed in: not stated |
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.
Products named in our analysis
- SOUND4 Impact/FIRST/PULSE/Eco <=2.x
Fix and mitigation
Action required
Patch when possible
WAF and other mitigations
Can a WAF block it? No. The attack needs local access to the machine, so a WAF is not on its path.
Also consider: shlex/execve-style APIs
Based on the attack vector (local or physical access). We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.
Remediation steps (AI-written)
Step-by-step remediation is generated for accounts on the Max plan, for CVEs that match a technology in their stack. Add this technology to your stack to see the fix checklist.
Exploitation evidence
- CISA KEV catalog
- Not listed as of our last sync.
- Public exploit code
- None on record in Exploit-DB, Metasploit, Nuclei templates or PoC-in-GitHub.
- CISA SSVC
- exploitation poc, automatable no, technical impact totalAssessed by CISA 5 Jan 2026 (SSVC 2.0.3). Exploitation is none, poc (public proof of concept) or active.
Timeline
- 30 Dec 2025Published
- 31 Dec 2025Analysed by vulneraibility.comsame day later
- 5 Jan 2026CISA SSVC assessment: exploitation poc6 days later
- 1 Oct 2026CVE record last updated269 days (about 9 months) later
Common questions
Is CVE-2022-50789 being exploited?
Not confirmed. CVE-2022-50789 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 4.2% probability of exploitation in the next 30 days.
How severe is CVE-2022-50789?
CVE-2022-50789 is rated High with a CVSS score of 8.5. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2022-50789?
Not known from our data. No patch reference has been recorded for CVE-2022-50789, which is not the same as no patch existing — a fix may have shipped without a tagged reference, or after this record was written. The vendor advisory is the only authority on whether a fix exists, and mitigations may be available regardless.
What does CVE-2022-50789 affect?
CVE-2022-50789 affects SOUND4 Impact/FIRST/PULSE/Eco <=2.x. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2022-50789?
Patch when released; restrict dns.php access and require auth.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
References
5 references in the CVE record, grouped by the tags the record gives them.
Advisories (2)
- zeroscience.mk /en/vulnerabilities/ZSL-2022-5733.php
- vulncheck.com /advisories/sound-impactfirstpulseeco-x-conditional-command-injection-via-dnsphp
Exploits (1)
- packetstormsecurity.com /files/170260/SOUND4-IMPACT-FIRST-PULSE-Eco-2.x-dns.php-Command-Injection.html
Other links (2)
- exchange.xforce.ibmcloud.com /vulnerabilities/247922
- sound4.com /
Where the data on this page comes from
- CVE List (CVE.org): description, affected versions, references; CVE Terms of Use
- NVD: CVSS and CPE data
- CISA Vulnrichment (ADP): SSVC decision points
- FIRST EPSS: exploit probability and percentile
Summary, impact and triage tags: written by our AI analysis pipeline from the sources above. Check them against the sources.
Similar CVEs
Get CVEs like this by email. Join the free digest: the CVEs we flag as major, all CVSS 8.0 or higher, in up to three emails a day (sent at 05:00, 11:00 and 15:00 UTC). Matching alerts to the products you run needs an account, and accounts are invite-only during the beta.