Loading vulnerability…
CVE-2025-20720 is an out-of-bounds write vulnerability in a WLAN access point (AP) driver caused by an incorrect bounds check. The flaw allows memory to be written past the intended buffer boundary during processing in the AP driver. Based on the available description, exploitation is possible remotely from a proximal or adjacent attacker, does not require prior code execution privileges, and does not require user interaction. Successful exploitation can result in escalation of privilege on the affected device.
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 is a small standalone Python exploit project for CVE-2025-20720, branded as 'PolyShell'. It contains four files: a README with exploitation workflow and examples, a Python exploit script (cve_2025_20720.py), a requirements.txt listing requests and urllib3, and a .gitignore. The exploit is not part of a larger framework. The main script is a threaded mass-exploitation tool targeting Adobe Commerce / Magento 2 instances. Its workflow is: detect Magento and version, discover a valid SKU, create a guest cart, upload a GIF89a/PHP polyglot through the guest cart item API, locate the uploaded file under Magento custom_options media paths, invoke the shell with a token and command to confirm RCE, and optionally clean up by deleting the shell. The code uses requests.Session with randomized User-Agent strings, disables TLS verification warnings, and supports single-target or file-based mass targeting with configurable threads. Notable hardcoded endpoints in the exploit include /magento_version for detection, /graphql and /rest/default/V1/products?searchCriteria[pageSize]=5 for SKU discovery, /rest/default/V1/guest-carts for cart creation, and /rest/default/V1/guest-carts/{cart_id}/items for the malicious upload. It expects the uploaded shell to become reachable under /pub/media/custom_options/quote/ or /media/custom_options/quote/. The shell payload is a PHP webshell embedded in a GIF polyglot, protected by a generated token and capable of executing arbitrary commands via multiple PHP execution functions, returning output markers, and self-deleting. Overall, this is a real exploit rather than a detector: it automates pre-auth arbitrary file upload to achieve remote code execution and includes operational features such as concurrency, output saving, debug logging, and cleanup.
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 and community write-ups. News coverage will land here when it surfaces.
No news coverage yet. Advisories and community discussion only.
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.