cve.bz

CVE-2016-3081 Apache Struts Command Injection Vulnerability

8.1 highKEVExploitEPSS 97%Fix available

High (8.1) in Apache Struts. In CISA KEV since 2026-10-08. EPSS 97% estimated probability of exploitation activity in the next 30 days. Fixed in org.apache.struts:struts2-core 2.3.20.3, 2.3.24.3, 2.3.28.1.

On this page
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.

Severity

CVSS 3.1

8.1 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
EPSS
97% (unchanged from 97% a week ago; 96% 30 days ago) estimated probability of exploitation activity in the next 30 days; 100th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-10-08, due 2026-10-11
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: total, assessed 2026-10-08. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-77 Improper Neutralization of Special Elements used in a Command
OWASP Top 10
A05:2025 Injection
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2016-3081 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2016-3081?via=ask-ai-copy and https://cve.bz/cve/CVE-2016-3081?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2016-3081 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2016-3081

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2016-3081](https://cve.bz/cve/badge/CVE-2016-3081.svg)](https://cve.bz/cve/CVE-2016-3081)

HTML:

<a href="https://cve.bz/cve/CVE-2016-3081"><img src="https://cve.bz/cve/badge/CVE-2016-3081.svg" alt="CVE-2016-3081"></a>

Affected

Versions

From the NVD's CPE matches.

ProductAffected
huawei:agile_controller-campus_firmwarev100r002c00
huawei:anyofficev200r005c00
huawei:anyofficev200r006c00
huawei:logcenterv100r001c10
huawei:logcenterv100r001c20
huawei:firehunter6000_firmwarev100r001c20
huawei:oceanstor_5300_v3_firmwarev300r001
huawei:oceanstor_5300_v3_firmwarev300r002
huawei:oceanstor_5300_v3_firmwarev300r003c00
huawei:oceanstor_5300_v3_firmwarev300r003c10
huawei:oceanstor_5500_v3_firmwarev300r001
huawei:oceanstor_5500_v3_firmwarev300r002
huawei:oceanstor_5500_v3_firmwarev300r003c00
huawei:oceanstor_5500_v3_firmwarev300r003c10
huawei:oceanstor_5600_v3_firmwarev300r001
huawei:oceanstor_5600_v3_firmwarev300r002
huawei:oceanstor_5600_v3_firmwarev300r003c00
huawei:oceanstor_5600_v3_firmwarev300r003c10
huawei:oceanstor_5800_v3_firmwarev300r001
huawei:oceanstor_5800_v3_firmwarev300r002
huawei:oceanstor_5800_v3_firmwarev300r003c00
huawei:oceanstor_5800_v3_firmwarev300r003c10
huawei:oceanstor_6800_v3_firmwarev300r001
huawei:oceanstor_6800_v3_firmwarev300r002
huawei:oceanstor_6800_v3_firmwarev300r003c00
huawei:oceanstor_6800_v3_firmwarev300r003c10
huawei:oceanstor_18500_v3_firmwarev300r001
huawei:oceanstor_18500_v3_firmwarev300r002
huawei:oceanstor_18500_v3_firmwarev300r003c00
huawei:oceanstor_18500_v3_firmwarev300r003c10
huawei:oceanstor_18500f_firmwarev300r001
huawei:oceanstor_18500f_firmwarev300r002
huawei:oceanstor_18500f_firmwarev300r003c00
huawei:oceanstor_18500f_firmwarev300r003c10
huawei:oceanstor_18800_v3_firmwarev300r001
huawei:oceanstor_18800_v3_firmwarev300r002
huawei:oceanstor_18800_v3_firmwarev300r003c00
huawei:oceanstor_18800_v3_firmwarev300r003c10
huawei:oceanstor_18800f_firmwarev300r001
huawei:oceanstor_18800f_firmwarev300r002
huawei:oceanstor_18800f_firmwarev300r003c00
huawei:oceanstor_18800f_firmwarev300r003c10
huawei:oceanstor_9000_firmwarev100r001c01
huawei:oceanstor_9000_firmwarev100r001c30
huawei:oceanstor_9000_firmwarev300r005c00
huawei:oceanstor_n8500_firmwarev200r001c09spc505
huawei:oceanstor_n8500_firmwarev200r001c91spc205
huawei:oceanstor_n8500_firmwarev200r001c91spc900
huawei:oceanstor_n8500_firmwarev200r001c91spc901
huawei:oceanstor_onebox_firmwarev100r003c10
apache:strutsfrom 2.3.20 before 2.3.20.3
apache:strutsfrom 2.3.21 before 2.3.24.3
apache:strutsfrom 2.3.25 before 2.3.28.1
oracle:flexcube_private_banking2.0.0.0
oracle:flexcube_private_banking2.0.1
oracle:flexcube_private_banking2.2.0
oracle:flexcube_private_banking12.0.1
oracle:flexcube_private_banking12.0.3
oracle:flexcube_private_banking12.1.0
oracle:micros_retail_xbri_loss_prevention10.0.1
oracle:micros_retail_xbri_loss_prevention10.5.0
oracle:micros_retail_xbri_loss_prevention10.6.0
oracle:micros_retail_xbri_loss_prevention10.7.0
oracle:micros_retail_xbri_loss_prevention10.8.0
oracle:micros_retail_xbri_loss_prevention10.8.1
oracle:siebel_e-billing7.1

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-8c6j-ffmf-q6vmMavenorg.apache.struts:struts2-core>=2.3.19 <2.3.20.32.3.20.3
GHSA-8c6j-ffmf-q6vmMavenorg.apache.struts:struts2-core>=2.3.21 <2.3.24.32.3.24.3
GHSA-8c6j-ffmf-q6vmMavenorg.apache.struts:struts2-core>=2.3.25 <2.3.28.12.3.28.1

Public exploits

Detection rules

Ways to detect this CVE, not exploit code: the nuclei template that checks a system for it, and the Suricata and Snort rules that name it. A rule set may ship a rule turned off, so check yours by its sid.

Attack patterns (CAPEC)

  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-40 Manipulating Writeable Terminal Devices Likelihood: High · Severity: Very High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-75 Manipulating Writeable Configuration Files Likelihood: High · Severity: Very High
  • CAPEC-76 Manipulating Web Input to File System Calls Likelihood: High · Severity: Very High
  • CAPEC-136 LDAP Injection Likelihood: High · Severity: High
  • CAPEC-183 IMAP/SMTP Command Injection Severity: Medium
  • CAPEC-248 Command Injection Likelihood: Medium · Severity: High

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON