Loading vulnerability…
In SmartBear ReadyAPI through versions 2.8.2 and 3.0.0, and SoapUI through 5.5, the Groovy 'Load Script' and 'Save Script' features are automatically executed when opening or saving a project. This behavior allows an attacker to craft a malicious project file containing arbitrary Groovy code, which will be executed on the victim's machine if the file is opened or saved, leading to arbitrary code execution.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository demonstrates a proof-of-concept (PoC) exploit for CVE-2019-12180, a vulnerability in SmartBear SoapUI (5.5 and earlier) and ReadyAPI (3.0.0, 2.8.2 and earlier) on Windows. The exploit leverages the 'afterLoadScript' feature in project XML files, which allows embedded Groovy scripts to execute automatically when the project is loaded. The provided XML file contains a payload that executes 'calc.exe' (the Windows calculator) as a demonstration of arbitrary code execution. The README explains the vulnerability, affected versions, and provides an example of a more advanced payload (a Groovy reverse shell). The exploit requires the victim to open the malicious XML project file in a vulnerable version of SoapUI or ReadyAPI, after which the payload is executed without further interaction. The repository consists of the PoC XML file and a README with technical details and payload examples.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
No public activity tracked yet. Mallory keeps watching.
No public activity observed for this vulnerability.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.