CVE-2020-35489 is an unrestricted file upload vulnerability in the Contact Form 7 WordPress plugin before version 5.3.2. According to the provided content, the flaw allows a filename to contain special characters, resulting in insufficient validation of uploaded files. This can permit an attacker to upload arbitrary files, including potentially executable server-side payloads, leading to remote code execution under vulnerable server configurations.
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 3 candidates 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.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A previously disclosed arbitrary file upload vulnerability affecting the same developer's software.
A specific vulnerability referenced in the context of a trojanized proof-of-concept exploit repository that led to malware infection when executed.
A vulnerability identifier used as bait in a trojanized fake PoC repository; the content does not describe the underlying flaw itself, but focuses on malicious code masquerading as an exploit for this CVE.
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.