A deserialization vulnerability in funadmin up to 7.1.0-rc4 affects the backend endpoint implemented by the getMember function in app/common/service/AuthCloudService.php. By manipulating the cloud_account argument, an attacker can cause the application to deserialize attacker-controlled data, enabling remote exploitation.
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.
Repository contains a minimal proof-of-concept for CVE-2026-2898 affecting FunAdmin <= 7.1.0-rc4. Structure: (1) README.md describing an insecure deserialization issue where `cloud_account` is passed to PHP `unserialize()` in `AuthCloudService::getMember`, and (2) exploit.py, a Python script that takes `--url` and `--payload` and POSTs the payload as `cloud_account` to `{target}/index.php`. The exploit’s capability is limited to delivering an attacker-controlled serialized string and printing the server response; it does not include gadget-chain construction, authentication bypass, or an RCE payload generator, so successful code execution depends on the target environment and available PHP gadget chains.
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.