PoC Monitor
← All CVEs
CVE-2026-7567published 1 May 2026 09:26 UTCData: JSON · API

Elemntor Temporary Login

Temporary Login <= 1.0.0 - Authentication Bypass to Account Takeover

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.

First public PoC 23 hafter publication · 2 May 2026
Public PoCs21 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS9.8critical · scored by CNA · CWE-288
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

elemntor Temporary Login
  • <= 1.0.0

Mitigation

The record names no fix. Check the vendor advisory below.

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published1 May 2026 · t = 0First public PoC2 May 2026 · t+23h

First public PoC 23 h after publication; not in CISA KEV. First PoC: amirhosseinjamshidi64/CVE-2026-7567-POC (created 2 May 2026, found by us: backfilled).

PoC repositories

Found on GitHub.

1 PoCs

PoCs 1
RepositoryCreatedStarsAssessment
amirhosseinjamshidi64/CVE-2026-7567-POC 2 May 2026 +23 h 1 PoC

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.

PoC characteristics

What to hunt for in your logs · from 1 PoC repo

Regex

Generated from PoC characteristics; not yet reviewed. Matches the request path and query.

GET /wp-admin/
(?i)^/wp-admin/\?(?:.*&)?temp-login-token\[\]=

Suricata

Template generated from PoC characteristics. Review before deploying.

GET /wp-admin/
alert http any any -> $HOME_NET [80,443] (msg:"GG PoC-Monitor CVE-2026-7567 elemntor Temporary Login exploit attempt"; flow:established,to_server; http.method; content:"GET"; http.uri; content:"/wp-admin/"; http.uri; content:"temp-login-token[]="; reference:url,poc.griffinguard.io/cve/CVE-2026-7567; classtype:web-application-attack; sid:9107129; rev:1;)

Sigma

Template generated from PoC characteristics. Review before deploying.

GET /wp-admin/
title: elemntor Temporary Login exploit attempt (CVE-2026-7567)
id: gg-pocmon-cve-2026-7567-9107129
status: experimental
description: Request pattern taken from public PoCs for CVE-2026-7567. Generated, not reviewed.
references:
  - https://poc.griffinguard.io/cve/CVE-2026-7567
logsource:
  category: webserver
detection:
  selection:
    cs-method: GET
    cs-uri-stem|contains|all:
      - '/wp-admin/'
    cs-uri-query|contains|all:
      - 'temp-login-token[]='
  condition: selection
falsepositives:
  - Authorized vulnerability scanning
level: critical
tags:
  - attack.initial_access
  - attack.t1190
  - cve.2026.7567