How severe is CVE-2014-1202?

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

Which packages are affected by CVE-2014-1202?

CVE-2014-1202 affects the following packages: com.smartbear.soapui:soapui (Maven). Ecosystems affected: Maven.

How do I fix CVE-2014-1202?

Update com.smartbear.soapui:soapui to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1202 is resolved across your whole dependency graph.

How do I detect CVE-2014-1202 in my Maven dependencies?

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

How do I mitigate CVE-2014-1202 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-2014-1202 actively exploited in the wild?

Yes. There are 3 known exploit references for CVE-2014-1202, including 1 documented proof-of-concept exploit on Exploit-DB and 2 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-2014-1202?

CVE-2014-1202 has an EPSS (Exploit Prediction Scoring System) score of 7.7%, placing it in the 95th 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 indicates relatively lower exploitation probability, though the CVSS severity should still guide your patching priority.

What type of vulnerability is CVE-2014-1202?

CVE-2014-1202 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.

When was CVE-2014-1202 published, and has it been updated?

CVE-2014-1202 was published on May 17, 2022 and was last updated on December 21, 2023. 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-2014-1202 — soapui

Fix: SmartBear/soapui@6373165

CVE-2014-1202 is a Code Injection vulnerability in com.smartbear.soapui:soapui. 3 public exploit or proof-of-concept references are indexed, so weaponization risk is real. A fix is available for com.smartbear.soapui:soapui — see the affected versions and patch details below.

Code injection via property expansion in SoapUI

Published

May 17, 2022

Updated

Dec 21, 2023

Affected

1 pkg

Patched

1 / 1

Exploits

3 known

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

EPSS Exploitation Probability

via FIRST.org ↗

7.7%probability of exploitation in next 30 days

Lower Risk0.00%

Lower risk than most CVEs95th percentile — riskier than 95% of all scored CVEsHighest risk

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

Real-World Exposure

1 pkg affected

☕com.smartbear.soapui:soapui

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

The WSDL/WADL import functionality in SoapUI before 4.6.4 allows remote attackers to execute arbitrary Java code via a crafted request parameter in a WSDL file.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
☕Maven	`com.smartbear.soapui:soapui`	all versions	4.6.4`com.smartbear.soapui:soapui:4.6.4`

Affected Products

2 products · 17 configurations

Application

soapuieviware

6 versions

2.5.13.0.13.53.5.13.63.6.1

Application

soapuismartbear

≤ 4.6.3

8 versions

4.04.0.14.54.5.14.5.24.6.04.6.14.6.2

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.

EDB-30908remotewindows

SoapUI 4.6.3 - Remote Code Execution

by Barak Tawily · Jan 14, 2014

Exploit-DB Source

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for com.smartbear.soapui:soapui, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.
Fix
Update com.smartbear.soapui:soapui to 4.6.4 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2014-1202 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.

Frequently Asked Questions

The WSDL/WADL import functionality in SoapUI before 4.6.4 allows remote attackers to execute arbitrary Java code via a crafted request parameter in a WSDL file.

O3 Security · Impact-Aware SCA

Is CVE-2014-1202 in your dependencies?

Find it across Maven, including transitive dependencies.

Scan my dependencies How O3 SCA works