Loading vulnerability…
CVE-2026-7567 is an authentication bypass vulnerability in the Temporary Login plugin for WordPress affecting versions up to and including 1.0.0. The flaw is in the maybe_login_temporary_user() function, which processes the temp-login-token GET parameter without verifying that the supplied value is a scalar string. By supplying the parameter as an array, an attacker can bypass the intended empty() validation path; sanitize_key() then yields an empty string, which is passed as the meta_value argument to get_users(). In this condition, WordPress ignores the empty meta_value and returns users associated with the temporary login token meta key, enabling login without possession of a valid temporary token. This allows unauthenticated authentication as any active temporary login user via a single crafted request.
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.
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos (1 hidden).
This repository is a small standalone Python proof-of-concept exploit for CVE-2026-7567 affecting the WordPress Temporary Login plugin <= 1.0.0. The repo contains only two files: a brief README describing the vulnerability and usage, and a single executable script `exploit.py` that serves as the exploit entry point. The script is not part of a larger framework. The exploit’s core capability is web-based authentication bypass leading to account takeover/session acquisition. It prompts the operator for a target WordPress base URL, then sends a GET request to the crafted path `wp-admin/?temp-login-token[]`. The code assumes the vulnerable plugin mishandles the `temp-login-token` parameter when supplied as an array-like parameter, resulting in an authenticated session being issued without valid credentials. After the request, the script inspects returned cookies for `wp-settings-time` as a success indicator, then attempts to confirm access by requesting the derived `wp-admin/` URL with the same cookies. If the response suggests dashboard/admin access, it reports success; otherwise it notes that the authenticated user may have limited privileges. Operationally, this is more than a detector because it actively attempts exploitation, reuses the session, and persists the cookies to `wordpress_cookies.txt` for manual browsing or follow-on actions. However, it does not include a post-exploitation command payload or shell, so its effect is limited to obtaining and validating a logged-in WordPress session. The exploit is therefore best classified as an operational PoC for authentication bypass/session takeover rather than a weaponized framework module.
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.
8 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A comparable WordPress plugin authentication bypass vulnerability mentioned for background context.
An authentication bypass vulnerability in WordPress Temporary Login, described as having a CVSS score of 9.8.
An authentication bypass vulnerability in the Temporary Login plugin for WordPress caused by improper input validation of the 'temp-login-token' GET parameter, allowing unauthenticated attackers to authenticate as any active temporary login user.
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.