CVE-2026-2144
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe Magic Login Mail or QR Code plugin for WordPress is vulnerable to Privilege Escalation in all versions up to, and including, 2.05. This is due to the plugin storing the magic login QR code image with a predictable, static filename (QR_Code.png) in the publicly accessible WordPress uploads directory during the email sending process. The file is only deleted after wp_mail() completes, creating an exploitable race condition window. This makes it possible for unauthenticated attackers to trigger a login link request for any user, including administrators, and then exploit the race condition between QR code file creation and deletion to obtain the login URL encoded in the QR code, thereby gaining unauthorized access to the targeted user's account.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe Magic Login Mail or QR Code WordPress plugin (versions up to 2.05) stores magic login QR code images with a predictable static filename (QR_Code.png) in the publicly accessible uploads directory during the email sending process. The file is deleted only after wp_mail() completes. This creates an exploitable race condition window where unauthenticated attackers can trigger login link requests for any user (including administrators), then access the QR code file during the creation/deletion window to decode the login URL and gain unauthorized access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify plugin installation and activationIn WordPress admin, go to Plugins > Installed Plugins and look for 'Magic Login Mail or QR Code'. Check if it shows as 'Active'. Alternatively, check the plugins directory at wp-content/plugins/ for a folder containing 'magic-login' or similar.Affected if Plugin is installed and active with version 2.05 or lower
-
Confirm plugin versionIn WordPress admin_plugins page, click on the plugin name to view details and note the version number. Compare against the affected range (versions up to and including 2.05).Affected if Installed version is 2.05 or lower (any version up to 2.05)
-
Check if QR code login feature is enabledNavigate to plugin settings (Settings > Magic Login or similar) and verify if QR Code or magic login feature is turned on. Look for options like 'Enable QR Code Login' or 'Send Magic Login Link'.Affected if QR code or magic login feature is enabled in plugin settings
-
Verify uploads directory is web-accessibleCheck wp-config.php for UPLOADBLOGSDIR or wp_upload_dir() path. Confirm the uploads folder (typically /wp-content/uploads/) is under the webroot and accessible via HTTP. A simple test: attempt to access yourdomain.com/wp-content/uploads/ directly in a browser.Affected if Uploads directory is publicly accessible under the webroot (not moved outside public_html or blocked by .htaccess)
-
Check for QR_Code.png in uploads directoryList files in /wp-content/uploads/ (or your configured upload path) and look for a file named 'QR_Code.png'. Use FTP, SSH, or file manager to inspect. Note: this file is temporary and only exists during active login email processing.Affected if QR_Code.png file exists in the uploads directory (indicates the race condition window is or was active)
A user is affected if the Magic Login Mail or QR Code plugin version 2.05 or lower is active with the QR code feature enabled and the uploads directory remains web-accessible, creating a race condition window where QR_Code.png can be intercepted.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedDisable the Magic Login Mail or QR Code plugin until a patched version is available, or implement immediate mitigation by moving QR code storage outside the webroot, using random unique filenames, or adding .htaccess rules to block direct access to the uploads directory.
Magic Login Mail or QR Code version 2.06
- Update the Magic Login Mail or QR Code plugin to version 2.06 or later via the WordPress admin dashboard under Plugins > All Plugins > Update Now, or run wp plugin update magic-login-mail-or-qr-code if using WP-CLI
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-2144 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-2144 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data