How severe is CVE-2011-2730?

No CVSS score has been assigned to CVE-2011-2730 yet. Review the advisory details and affected package list to assess your exposure.

Which packages are affected by CVE-2011-2730?

CVE-2011-2730 affects the following packages: org.springframework:spring-core (Maven), org.springframework:spring-core (Maven), org.springframework:spring-core (Maven). Ecosystems affected: Maven.

How do I fix CVE-2011-2730?

Update org.springframework:spring-core to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2730 is resolved across your whole dependency graph.

How do I detect CVE-2011-2730 in my Maven dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

How do I mitigate CVE-2011-2730 if there is no patch (or I can't update yet)?

Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Is CVE-2011-2730 actively exploited in the wild?

No public exploit code has been indexed for CVE-2011-2730 yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

What is the EPSS score for CVE-2011-2730?

CVE-2011-2730 has an EPSS (Exploit Prediction Scoring System) score of 11.8%, placing it in the 96th percentile of all CVEs. EPSS is maintained by FIRST.org and estimates the probability that a vulnerability will be exploited in the wild within the next 30 days. This score warrants monitoring and prompt remediation.

What type of vulnerability is CVE-2011-2730?

CVE-2011-2730 is classified as CWE-16 (CWE-16). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation.

When was CVE-2011-2730 published, and has it been updated?

CVE-2011-2730 was published on May 17, 2022 and was last updated on December 5, 2024. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

☕ Maven

Not in CISA KEV

CVE-2011-2730 — spring-core

Fix: spring-projects/spring-framework@62ccc8d

CVE-2011-2730 is a CWE-16 vulnerability in org.springframework:spring-core. EPSS puts its 30-day exploitation probability at 11.8% (96th percentile). A fix is available for org.springframework:spring-core — see the affected versions and patch details below.

Improper Neutralization of Directives in Dynamically Evaluated Code in Spring Framework

Published

May 17, 2022

Updated

Dec 5, 2024

Affected

3 pkgs

Patched

3 / 3

Exploits

None indexed

Exploitation data as of Oct 24, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗

11.8%probability of exploitation in next 30 days

Moderate Risk0.00%

Lower risk than most CVEs96th percentile — riskier than 96% of all scored CVEsHighest risk

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

Real-World Exposure

3 pkgs affected

☕org.springframework:spring-core☕org.springframework:spring-core☕org.springframework:spring-core

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Maven packages — download data is not available via public APIs for these ecosystems.

Description

VMware SpringSource Spring Framework before 2.5.6.SEC03, 2.5.7.SR023, and 3.x before 3.0.6, when a container supports Expression Language (EL), evaluates EL expressions in tags twice, which allows remote attackers to obtain sensitive information via a (1) name attribute in a (a) spring:hasBindErrors tag; (2) path attribute in a (b) spring:bind or (c) spring:nestedpath tag; (3) arguments, (4) code, (5) text, (6) var, (7) scope, or (8) message attribute in a (d) spring:message or (e) spring:theme tag; or (9) var, (10) scope, or (11) value attribute in a (f) spring:transform tag, aka "Expression Language Injection."

Affected Packages

3 total 3 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework:spring-core`	≥ 3.0.0&&< 3.0.6	3.0.6`org.springframework:spring-core:3.0.6`
☕Maven	`org.springframework:spring-core`	all versions	2.5.6.SEC03`org.springframework:spring-core:2.5.6.SEC03`
☕Maven	`org.springframework:spring-core`	≥ 2.5.7.SR0&&< 2.5.7.SR023	2.5.7.SR023`org.springframework:spring-core:2.5.7.SR023`

Affected Products

1 product · 17 configurations

Application

spring frameworkspringsource

≤ 3.0.5

13 versions

2.5.02.5.12.5.22.5.32.5.42.5.52.5.62.5.73.0.03.0.13.0.23.0.3

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for org.springframework:spring-core, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update org.springframework:spring-core to 3.0.6 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2011-2730 is resolved across your whole dependency graph.
Workarounds
Stop passing untrusted input into the interpreter or shell: call the affected binary with an argument array rather than a composed command string, reject anything outside a strict allowlist of expected values, and run the component under an account that cannot reach beyond the work it legitimately does.

Fixing This On Your OS

If you run this on a Linux distribution, patch through your package manager against the distro's own security advisory below — it tracks the exact backported fix for your release, which can ship on a different timeline (and sometimes a different severity) than the upstream project.

Red HatImportant

This flaw was originally reported as resulting in information disclosure only, and was therefore assessed as having low security impact. On this basis, it was planned that future updates to JBoss products may address this flaw. New research [0] has now shown that this flaw can lead to remote code execution. The…

Product	Fixed in	Advisory
JBEWP 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0196
JBEWP 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0195
JBoss Enterprise BRMS Platform 5.3	see advisory	RHSA-2013:0221
Red Hat JBoss Enterprise Application Platform 5.2	see advisory	RHSA-2013:0194
Red Hat JBoss Enterprise Application Platform 5 for RHEL 5	`aopalliance-0:1.0-5.2.jdk6.ep5.el5`	RHSA-2013:0192
Red Hat JBoss Enterprise Application Platform 5 for RHEL 6	`aopalliance-0:1.0-5.3.ep5.el6`	RHSA-2013:0191
Red Hat JBoss Portal 5.2	see advisory	RHSA-2013:0953
Red Hat JBoss SOA Platform 5.3	see advisory	RHSA-2013:0533

Frequently Asked Questions

O3 Security · Impact-Aware SCA

Is CVE-2011-2730 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works