What is the CVSS score of CVE-2019-10774?

CVE-2019-10774 has a CVSS 3.1 base score of 9.8 (Critical). CVSS vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 4.6%.

Is there a public PoC exploit available for CVE-2019-10774?

Yes, a public proof-of-concept exploit is available for CVE-2019-10774. Prioritise patching immediately. EPSS: 4.6%.

Is there a patch available for CVE-2019-10774?

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

Php Shellcommand CVE-2019-10774

CRITICAL

OS Command Injection (CWE-78)

2019-12-30 report@snyk.io

RCE Command Injection Php Shellcommand

9.8

CVSS 3.1 · NVD

Severity by source

NVD PRIMARY

9.8 CRITICAL

AV:N/AC:L/PR:N/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:N/UI:N/S:U/C:H/I:H/A:H

Attack Vector

Network

Attack Complexity

Low

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Dec 30, 2019 - 17:15 nvd

CRITICAL 9.8

DescriptionNVD

php-shellcommand versions before 1.6.1 have a command injection vulnerability. Successful exploitation could lead to arbitrary code execution.

AnalysisAI

php-shellcommand versions before 1.6.1 have a command injection vulnerability. Rated critical severity (CVSS 9.8), this vulnerability is remotely exploitable, no authentication required, 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. php-shellcommand versions before 1.6.1 have a command injection vulnerability. Successful exploitation could lead to arbitrary code execution. Affected products include: Php-Shellcommand Project Php-Shellcommand. Version information: before 1.6.1.

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.