CVE-2022-50791
Unauthenticated HTTP POST to ping.php enables command execution (RCE).
Is CVE-2022-50791 being exploited?
Not confirmed. CVE-2022-50791 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 3.8% probability of exploitation in the next 30 days.
How severe is CVE-2022-50791?
CVE-2022-50791 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-50791?
Not known from our data. No patch reference has been recorded for CVE-2022-50791, 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-50791 affect?
CVE-2022-50791 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-50791?
Apply patch when available; restrict/disable ping.php access.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated RCE via ping.php; attacker can run OS commands and affect /tmp files.
Immediate action required
- affected1.30
- affected1.2
- affected1.16
- affectedVersion 2: 1.1/2.15
- affected1.1/2.4.29
- affected1.11
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.