What is the CVSS score of CVE-2022-26481?

CVE-2022-26481 has a CVSS 3.1 base score of 8.8 (High). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 1.6%.

Is there a public PoC exploit available for CVE-2022-26481?

Yes, a public proof-of-concept exploit is available for CVE-2022-26481. Prioritise patching immediately. EPSS: 1.6%.

Studio X30 Firmware CVE-2022-26481

HIGH

OS Command Injection (CWE-78)

2022-07-17 cve@mitre.org

Command Injection Studio X30 Firmware Studio X70 Firmware G7500 Firmware Studio X50 Firmware

8.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

8.8 HIGH

AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Primary rating from NVD · only source for this CVE.

CVSS VectorNVD

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

Low

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Jul 17, 2022 - 23:15 nvd

HIGH 8.8

DescriptionNVD

An issue was discovered in Poly Studio before 3.7.0. Command Injection can occur via the CN field of a Create Certificate Signing Request (CSR) action.

AnalysisAI

An issue was discovered in Poly Studio before 3.7.0. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available and no vendor patch available.

Technical ContextAI

This vulnerability is classified as OS Command Injection (CWE-78), which allows attackers to execute arbitrary operating system commands on the host. An issue was discovered in Poly Studio before 3.7.0. Command Injection can occur via the CN field of a Create Certificate Signing Request (CSR) action. Affected products include: Poly Studio X30 Firmware, Poly Studio X70 Firmware, Poly G7500 Firmware, Poly Studio X50 Firmware. Version information: before 3.7.0..

RemediationAI

No vendor patch is available at time of analysis. Monitor vendor advisories for updates. Avoid passing user input to shell commands. Use language-specific APIs instead of shell execution. Apply strict input validation with allowlists.