Loading vulnerability…
The Magic Login Mail or QR Code plugin for WordPress is vulnerable to privilege escalation in all versions up to and including 2.05 due to insecure handling of a generated magic-login QR code image. During the email sending process, the plugin writes the QR code to the publicly accessible WordPress uploads directory using a predictable, static filename (QR_Code.png). The file is only deleted after wp_mail() completes, creating a race condition window between file creation and deletion. An unauthenticated attacker can trigger a magic login link request for an arbitrary user (including administrators) and, during the race window, retrieve QR_Code.png from uploads and decode it to obtain the victim’s magic login URL, enabling unauthorized login as that 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 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.
4 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.