CVE-2026-66398 is a remote code execution vulnerability affecting phpMyFAQ versions prior to 4.1.6. The flaw resides in the configuration API and stems from unsafe handling of the updater-related setting upgrade.lastDownloadedPackage. An authenticated administrator with both CONFIGURATION_EDIT and ATTACHMENT_ADD privileges can upload a malicious ZIP archive as an attachment, modify the updater configuration to reference the stored archive path, and cause its contents to be extracted into the application root. By placing attacker-controlled PHP content in a web-accessible location, the attacker can write arbitrary PHP files and execute code in the context of the web server user.
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 public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
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.
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.