CVE-2026-7567

CRITICALNVD 9.89.8
EchelonGraph scoreMEDIUM confidence

Score 9.8 from GitHub Security Advisory (severity: CRITICAL) published 2026-05-01. NVD baseline CVSS 9.8; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Elevated
9.8
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 9%CVSS: 9.8Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

CVSS v3
9.8
EG Score
9.8(medium)
EG Risk
75(Track)
EG Risk 75/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity98% × 45%
Exploitation40% × 40%
Automatability100% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
94.8%
KEV
Not listed

Published

May 1, 2026

Last Modified

May 1, 2026

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 37× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

Showing the most recent 100 of 150 total refreshes for this CVE.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:22 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-22 14:08 UTCEPSS rescore
  6. 2026-07-21 15:25 UTCEPSS rescore
  7. 2026-07-21 15:25 UTCEPSS rescore
  8. 2026-07-20 17:08 UTCEPSS rescore
  9. 2026-07-19 14:31 UTCEPSS rescore
  10. 2026-07-19 02:29 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-16 17:03 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-13 22:31 UTCEPSS rescore
  16. 2026-07-12 05:46 UTCEPSS rescore
  17. 2026-07-11 08:27 UTCEPSS rescore
  18. 2026-07-09 19:10 UTCEPSS rescore
  19. 2026-07-09 19:10 UTCEPSS rescore
  20. 2026-07-08 15:16 UTCEPSS rescore
  21. 2026-07-08 15:16 UTCEPSS rescore
  22. 2026-07-07 13:46 UTCEPSS rescore
  23. 2026-07-07 13:46 UTCEPSS rescore
  24. 2026-07-06 16:27 UTCEPSS rescore
  25. 2026-07-06 16:27 UTCEPSS rescore
Show 75 more
  1. 2026-07-05 02:31 UTCEPSS rescore
  2. 2026-07-05 02:30 UTCEPSS rescore
  3. 2026-07-04 06:31 UTCEPSS rescore
  4. 2026-07-04 06:31 UTCEPSS rescore
  5. 2026-07-01 15:07 UTCEPSS rescore
  6. 2026-06-30 23:22 UTCEPSS rescore
  7. 2026-06-29 14:06 UTCEPSS rescore
  8. 2026-06-28 04:56 UTCEPSS rescore
  9. 2026-06-27 03:08 UTCEPSS rescore
  10. 2026-06-25 13:50 UTCEPSS rescore
  11. 2026-06-24 14:05 UTCEPSS rescore
  12. 2026-06-23 21:33 UTCEPSS rescore
  13. 2026-06-19 19:26 UTCEPSS rescore
  14. 2026-06-19 19:26 UTCEPSS rescore
  15. 2026-06-18 17:52 UTCEPSS rescore
  16. 2026-06-18 17:52 UTCEPSS rescore
  17. 2026-06-17 17:53 UTCEPSS rescore
  18. 2026-06-16 17:53 UTCEPSS rescore
  19. 2026-06-15 17:49 UTCEPSS rescore
  20. 2026-06-15 17:49 UTCEPSS rescore
  21. 2026-06-15 04:09 UTCGHSA enrichment
  22. 2026-06-15 00:14 UTCGHSA enrichment
  23. 2026-06-14 20:16 UTCGHSA enrichment
  24. 2026-06-14 16:25 UTCGHSA enrichment
  25. 2026-06-14 09:12 UTCGHSA enrichment
  26. 2026-06-13 23:00 UTCEPSS rescore
  27. 2026-06-12 23:12 UTCEPSS rescore
  28. 2026-06-12 23:12 UTCEPSS rescore
  29. 2026-06-12 12:44 UTCGHSA enrichment
  30. 2026-06-12 08:53 UTCGHSA enrichment
  31. 2026-06-12 05:00 UTCGHSA enrichment
  32. 2026-06-12 01:09 UTCGHSA enrichment
  33. 2026-06-11 21:17 UTCGHSA enrichment
  34. 2026-06-11 17:26 UTCGHSA enrichment
  35. 2026-06-11 14:00 UTCEPSS rescore
  36. 2026-06-11 11:31 UTCGHSA enrichment
  37. 2026-06-11 07:33 UTCGHSA enrichment
  38. 2026-06-11 03:42 UTCGHSA enrichment
  39. 2026-06-10 22:19 UTCEPSS rescore
  40. 2026-06-10 19:37 UTCGHSA enrichment
  41. 2026-06-10 15:46 UTCGHSA enrichment
  42. 2026-06-10 13:22 UTCEPSS rescore
  43. 2026-06-10 11:56 UTCGHSA enrichment
  44. 2026-06-10 08:05 UTCGHSA enrichment
  45. 2026-06-10 03:19 UTCGHSA enrichment
  46. 2026-06-09 23:27 UTCGHSA enrichment
  47. 2026-06-09 18:49 UTCGHSA enrichment
  48. 2026-06-09 14:57 UTCGHSA enrichment
  49. 2026-06-09 11:06 UTCGHSA enrichment
  50. 2026-06-09 07:16 UTCGHSA enrichment
  51. 2026-06-09 03:25 UTCGHSA enrichment
  52. 2026-06-08 23:33 UTCGHSA enrichment
  53. 2026-06-08 14:44 UTCGHSA enrichment
  54. 2026-06-08 14:17 UTCEPSS rescore
  55. 2026-06-08 10:53 UTCGHSA enrichment
  56. 2026-06-08 07:01 UTCGHSA enrichment
  57. 2026-06-08 03:11 UTCGHSA enrichment
  58. 2026-06-07 23:20 UTCGHSA enrichment
  59. 2026-06-07 19:29 UTCGHSA enrichment
  60. 2026-06-07 15:38 UTCGHSA enrichment
  61. 2026-06-07 15:25 UTCEPSS rescore
  62. 2026-06-07 11:47 UTCGHSA enrichment
  63. 2026-06-07 07:56 UTCGHSA enrichment
  64. 2026-06-07 04:05 UTCGHSA enrichment
  65. 2026-06-07 00:13 UTCGHSA enrichment
  66. 2026-06-06 20:22 UTCGHSA enrichment
  67. 2026-06-06 16:31 UTCGHSA enrichment
  68. 2026-06-06 12:40 UTCGHSA enrichment
  69. 2026-06-06 08:49 UTCGHSA enrichment
  70. 2026-06-06 04:58 UTCGHSA enrichment
  71. 2026-06-06 01:06 UTCGHSA enrichment
  72. 2026-06-05 22:47 UTCEPSS rescore
  73. 2026-06-05 21:16 UTCGHSA enrichment
  74. 2026-06-05 17:25 UTCGHSA enrichment
  75. 2026-06-05 13:34 UTCGHSA enrichment

Publicly available exploits

(1 reference)

Working exploit code is in the public domain (1 Exploit-DB entry). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-52575
    First seen May 26, 2026

    Wordpress Temporary Login Plugin 1.0.0 - 'temp-login-token' Authentication Bypass to Account Takeover

    Open source ↗

Frequently asked(5)

What is CVE-2026-7567?
CVE-2026-7567 is a critical vulnerability published on May 1, 2026. 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 maybelogintemporaryuser() function, which fails to verify that the 'temp-login-token' GET parameter is a scalar string before…
When was CVE-2026-7567 disclosed?
CVE-2026-7567 was first published in the National Vulnerability Database on May 1, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-7567 actively exploited?
CVE-2026-7567 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 94.8% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-7567?
CVE-2026-7567 has a CVSS v3 base score of 9.8 (NVD).
How do I remediate CVE-2026-7567?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-7567, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-7567

Explore →

Is Your Infrastructure Affected by CVE-2026-7567?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.