How severe is CVE-2018-1273?

CVE-2018-1273 has a CVSS score of 9.8/10, rated CRITICAL. Immediate patching is strongly recommended.

Which packages are affected by CVE-2018-1273?

CVE-2018-1273 affects the following packages: org.springframework.data:spring-data-commons (Maven), org.springframework.data:spring-data-commons (Maven). Ecosystems affected: Maven.

How do I fix CVE-2018-1273?

Update org.springframework.data:spring-data-commons to version 1.13.11 or later. Run your dependency manager's update command and verify no transitive dependencies pin the vulnerable version. Use O3 Security's SCA scanner to confirm the fix is applied across your entire dependency tree.

Is CVE-2018-1273 actively exploited in the wild?

Yes. There are 11 known exploit references for CVE-2018-1273, including 7 in-the-wild exploitations observed on GitHub and other sources. Treat this as actively exploitable and prioritize patching immediately. All exploit code should only be run in an isolated sandbox environment for research or authorized testing — never against production systems without explicit written authorization.

What is the EPSS score for CVE-2018-1273?

CVE-2018-1273 has an EPSS (Exploit Prediction Scoring System) score of 94.3%, placing it in the 100th 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. A score above 50% indicates significantly elevated exploitation risk — immediate patching is strongly recommended.

Is CVE-2018-1273 in the CISA Known Exploited Vulnerabilities catalog?

Yes. CVE-2018-1273 (VMware Tanzu Spring Data Commons Property Binder Vulnerability) was added to CISA's Known Exploited Vulnerabilities (KEV) catalog on 2022-03-25. CISA required all US federal civilian agencies to remediate this vulnerability by 2022-04-15. The required action was: Apply updates per vendor instructions. This CVE has been used in known ransomware campaigns. Being listed in the KEV catalog is the strongest possible confirmation of active exploitation — treat this as a critical priority.

What type of vulnerability is CVE-2018-1273?

CVE-2018-1273 is classified as Code Injection (CWE-94). This weakness type describe the underlying flaw category, which helps determine the potential impact and the right class of mitigation. This is a high-impact weakness class that often enables remote code execution or data exposure.

Is there exploit tooling available for CVE-2018-1273?

A Nuclei detection template exists for CVE-2018-1273, meaning automated scanners can fingerprint it. Public exploit tooling significantly increases real-world risk — prioritize patching and ensure detection coverage. Exploit tooling should only ever be used in isolated, authorized testing environments.

When was CVE-2018-1273 published, and has it been updated?

CVE-2018-1273 was published on April 11, 2018 and was last updated on April 10, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

CISA KEV·Added 2022-03-25 — agencies required to remediate by 2022-04-15 · Ransomware

☕ Maven

CVE-2018-1273

CRITICAL

Spring Data Commons remote code injection vulnerability

Also known asGHSA-4fq3-mr56-cg6r

Published

Apr 11, 2018

Updated

Apr 10, 2026

Affected

2 pkgs

Patched

2 / 2

Exploits

11 known

EPSS Exploitation Probability

via FIRST.org ↗

94.3%probability of exploitation in next 30 days

Very High Risk100th percentile0.00%

EPSS (Exploit Prediction Scoring System) is a daily probability model maintained by FIRST.org. It estimates the likelihood a CVE will be exploited in production environments within the next 30 days, derived from real-world threat intelligence signals.

Blast Radius

2 pkgs affected

☕org.springframework.data:spring-data-commons☕org.springframework.data:spring-data-commons

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

Spring Data Commons, versions prior to 1.13 to 1.13.10, 2.0 to 2.0.5, and older unsupported versions, contain a property binder vulnerability caused by improper neutralization of special elements. An unauthenticated remote malicious user (or attacker) can supply specially crafted request parameters against Spring Data REST backed HTTP resources or using Spring Data's projection-based request payload binding hat can lead to a remote code execution attack.

Affected Packages

2 total 2 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`org.springframework.data:spring-data-commons`	≥ 1.13.0&&< 1.13.11	1.13.11
☕Maven	`org.springframework.data:spring-data-commons`	≥ 2.0.0&&< 2.0.6	2.0.6

Exploits & PoCs

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.