Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
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 references exist, 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 Sep 18, 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 CVEs94th percentile — riskier than 94% of all scored CVEsHighest risk

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.

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
EcosystemPackageVulnerable rangeFix
Mavencom.smartbear.soapui:soapuiall versions4.6.4com.smartbear.soapui:soapui:4.6.4
Exploits & PoCs
3

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

Detection & mitigation playbook

Open-source dependency
  1. 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.

  2. 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.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 Security's impact-aware SCA analyses which vulnerable code paths your application actually calls, so a match like CVE-2014-1202 can be triaged on real exposure rather than presence alone.

Tailored to CVE-2014-1202. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

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?

O3 Security finds CVE-2014-1202 across Maven dependencies, including transitive ones, and its impact-aware SCA ranks findings by whether your code actually calls the vulnerable path.

CVE-2014-1202: soapui | O3 Security