Loading vulnerability…
CubeCart 5.0.0 through 5.2.0 contains an unsafe deserialization flaw in Cubecart::_basket in classes/cubecart.class.php. The method uses PHP unserialize() on attacker-controlled data supplied via the shipping parameter, allowing remote attackers to inject arbitrary serialized PHP objects. By supplying a crafted serialized object, an attacker can alter object state during deserialization; the published example demonstrates modification of application configuration through the Config object. This is a PHP object injection / deserialization of untrusted data issue.
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.
No valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
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.
2 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
PHP unserialize on untrusted input vulnerability allowing modification of application configuration.
Unsafe PHP unserialize() on untrusted input enabling an attacker to modify application configuration (and potentially more, depending on available gadget chains).
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.