BigAntSoft BigAnt Server versions up to and including 5.6.06 allow unauthenticated remote attackers to register an administrative account via the default SaaS registration mechanism. With administrative privileges, attackers can leverage the 'Cloud Storage Addin' to upload and execute arbitrary PHP code, resulting in unauthenticated remote code execution on the server.
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 contains a Go-based exploit for CVE-2025-0364, targeting BigAntSoft BigAnt Server (Windows, versions 5.6.06 and below). The exploit leverages an insecure SaaS registration process and a file upload vulnerability to achieve unauthenticated remote code execution (RCE). The attack chain involves solving a CAPTCHA to register a new administrative SaaS account, using that account to access the Cloud Storage Add-in, uploading a PHP reverse shell, and then triggering the shell to gain SYSTEM-level access on the server. The exploit is operational and provides a working reverse shell payload in PHP, which connects back to an attacker-controlled host and port. The main exploit logic is implemented in 'cve-2025-0364.go', which is the only code file in the repository. The repository also includes build files (Makefile, Dockerfile), Go module files, and documentation. Multiple HTTP endpoints used in the attack chain are fingerprintable, including those for registration, CAPTCHA, file upload, and payload execution. The exploit is not part of a larger framework but uses the 'vulncheck-oss/go-exploit' library for its core logic.
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.