CVE-2022-26481

Exp

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.

Published: 2022-07-17 Last update: 2024-11-21 Assigner: [email protected] Source: [email protected]
NVD Status：Modified，CVE State: published
View at NVD, CVE.org, EUVD

CVE-2022-26481 is rated High Exploit Risk (75.7/100): CVSS High severity, with medium exploitation likelihood (EPSS 3.36%). 1 public exploit reference(s) are indexed (Exploit-DB). Public exploits are available—assess exposure, apply mitigations, and prioritize patching.

Risk is dynamic; we continuously reassess and refresh what is shown on this page as upstream context changes.

Public exploit references (Exploit-DB) for CVE-2022-26481

EDB-ID Source Kind Published Link
— nvd_ref exploit_tag Exploit-DB ↗

Exploit prediction scoring system (EPSS) score for CVE-2022-26481

EPSS lead: Daily EPSS estimates relative likelihood of exploitation; percentile ranks this CVE among scored vulnerabilities (higher = more severe relative rank).

# Date Old EPSS score New EPSS score Delta (New - Old)
1 2025-11-21 8.24% 3.36% -4.87%
2 2025-11-18 3.36% 8.24% +4.87%
3 2025-09-06 — 3.36% —

Full EPSS history (18 records total)

Common vulnerability scoring system (CVSS) metrics for CVE-2022-26481

CVSS metrics for this CVE.

Base score Version Severity Vector Exploitability Impact Score source
8.8 3.1 HIGH
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H Click to expand
Attack vector (AV:N)
Could be attacked over the internet or any normal routed network—not just someone sitting at the machine.
Attack complexity (AC:L)
Once they can reach the bug, pulling it off is straightforward—no weird race conditions or rare setup.
Privileges required (PR:L)
A normal user session is enough; they don’t have to be admin.
User interaction (UI:N)
Nobody has to click “OK” or open a trap file; it can work without a victim helping.
Scope (S:U)
Damage stays in the same “trust bubble” as the broken component—no big spill into unrelated systems.
Confidentiality (C:H)
Serious risk that confidential data gets exposed in a big way.
Integrity (I:H)
They could widely tamper with or forge data—trust in the data is badly hurt.
Availability (A:H)
Could take the service down hard or make it unusable for people who depend on it.
 2.8 5.9 [email protected]

Weakness enumeration for CVE-2022-26481

Affected software / configurations for CVE-2022-26481

Vendor Product Version Raw CPE
poly studio_x30_firmware < 3.7.0 cpe:2.3:o:poly:studio_x30_firmware:*:*:*:*:*:*:*:*
poly studio_x70_firmware < 3.7.0 cpe:2.3:o:poly:studio_x70_firmware:*:*:*:*:*:*:*:*
poly g7500_firmware < 3.7.0 cpe:2.3:o:poly:g7500_firmware:*:*:*:*:*:*:*:*
poly studio_x50_firmware < 3.7.0 cpe:2.3:o:poly:studio_x50_firmware:*:*:*:*:*:*:*:*

References for CVE-2022-26481

cvelogic Threat Intelligence