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

CVE-2022-1509 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: 4.5%.

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

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

Is there a patch available for CVE-2022-1509?

Yes, a patch is available for CVE-2022-1509. Update the affected software to the latest version immediately.

Control Panel CVE-2022-1509

HIGH

Command Injection (CWE-77)

2022-04-28 security@huntr.dev

RCE Command Injection Control Panel

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

Apr 28, 2022 - 10:15 nvd

HIGH 8.8

DescriptionNVD

Command Injection Vulnerability in GitHub repository hestiacp/hestiacp prior to 1.5.12. An authenticated remote attacker with low privileges can execute arbitrary code under root context.

AnalysisAI

Command Injection Vulnerability in GitHub repository hestiacp/hestiacp prior to 1.5.12. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable, low attack complexity. Public exploit code available.

Technical ContextAI

This vulnerability is classified as Command Injection (CWE-77), which allows attackers to inject arbitrary commands into system command execution. Command Injection Vulnerability in GitHub repository hestiacp/hestiacp prior to 1.5.12. An authenticated remote attacker with low privileges can execute arbitrary code under root context. Affected products include: Hestiacp Control Panel. Version information: prior to 1.5.12..

RemediationAI

A vendor patch is available. Apply the latest security update as soon as possible. Use parameterized APIs, avoid shell execution, validate input with strict allowlists.