What is the CVSS score of CVE-2016-3081?

CVE-2016-3081 has a CVSS 3.0 base score of 8.1 (High). CVSS vector: CVSS:3.0/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. EPSS exploitation probability: 94.0%.

Is there a public PoC exploit available for CVE-2016-3081?

Yes, a public proof-of-concept exploit is available for CVE-2016-3081. Prioritise patching immediately. EPSS: 94.0%.

Is there a patch available for CVE-2016-3081?

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

Struts CVE-2016-3081

HIGH

Command Injection (CWE-77)

2016-04-26 secalert@redhat.com

Command Injection RCE Apache Struts Siebel E Billing

8.1

CVSS 3.0 · NVD

Severity by source

NVD PRIMARY

8.1 HIGH

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

Attack Vector

Network

Attack Complexity

High

Privileges Required

None

User Interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

CVE Published

Apr 26, 2016 - 14:59 cve.org

HIGH 8.1

DescriptionCVE.org

AnalysisAI

Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to. Rated high severity (CVSS 8.1), this vulnerability is remotely exploitable, no authentication required. Public exploit code available and EPSS exploitation probability 94.0%.

Technical ContextAI

This vulnerability is classified as Command Injection (CWE-77), which allows attackers to inject arbitrary commands into system command execution. Apache Struts 2.3.19 to 2.3.20.2, 2.3.21 to 2.3.24.1, and 2.3.25 to 2.3.28, when Dynamic Method Invocation is enabled, allow remote attackers to execute arbitrary code via method: prefix, related to chained expressions. Affected products include: Apache Struts, Oracle Siebel E-Billing.

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.