Skip to content
Fencer Intel
critical 9.8

CVE-2026-7567 json

Temporary Login <= 1.0.0 - Authentication Bypass to Account Takeover

published 6mo ago modified 4mo ago also EUVD-2026-26490

cvss
9.8
version 3.1, CNA
cisa kev
Not listed
not in CISA's catalog
epss
9.2%
EPSS 9.2% chance of exploitation in 30 days, percentile 95%
public exploits
1
Exploit-DB

Summary

The Temporary Login plugin for WordPress is vulnerable to Authentication Bypass in versions up to and including 1.0.0. This is due to improper input validation in the maybe_login_temporary_user() function, which fails to verify that the 'temp-login-token' GET parameter is a scalar string before processing it. When the parameter is supplied as an array, PHP's empty() check is bypassed and sanitize_key() returns an empty string, which is then passed as the meta_value to get_users(). WordPress ignores an empty meta_value and returns all users matching the meta_key '_temporary_login_token', allowing authentication without a valid token. This makes it possible for unauthenticated attackers to authenticate as any active temporary login user by sending a single crafted GET request.

Is CVE-2026-7567 in your stack? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.

Check with Fencer

Timeline

  1. Published
  2. First public exploit (EDB-52575)

CISA SSVC

Exploitation
none
Automatable
yes
Technical impact
total
Assessed
6mo ago

Exploit prediction

9.25% chance of exploitation in the next 30 days, higher than 95% of all scored CVEs (FIRST EPSS, 2026-11-11).

Exploits and checks

  • EDB-52575 Wordpress Temporary Login Plugin 1.0.0 - 'temp-login-token' Authentication Bypass to Account Takeover webapps, 2026-05-26

CVSS scores

assigned by version score vector
CNA 3.1 9.8 CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Affected products

  • elemntor Temporary Login

Classification

Weakness
  • CWE-288 Authentication Bypass Using an Alternate Path or Channel
Technology feeds

References

Sources

Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.