CVE-2026-2128

MEDIUMNVD 5.35.3
EchelonGraph scoreMEDIUM confidence

Score 5.3 from GitHub Security Advisory published 2026-05-29. NVD baseline CVSS 5.3; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: epss, ghsa, nvd
Trending — 3 sources updated this week
5.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 5.3Exploit: NoneExposed: 0

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

The Breeze plugin for WordPress is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in all versions up to, and including, 2.5.2 This is due to improper verification of the wordpress_logged_in_ cookie in the inc/cache/execute-cache.php file when the "Cache Logged-in Users" setting is enabled. The plugin parses the username directly from the cookie value (e.g., username|hash) using substr() to retrieve the corresponding cache file but fails to verify the session's cryptographic signature or validity with WordPress core. This makes it possible for unauthenticated attackers to supply a crafted cookie (e.g., wordpress_logged_in_fake=admin|fake) to trick the plugin into serving the cached HTML content generated for an administrator, leading to the disclosure of sensitive information such as private posts (including their full content), the Admin Bar, WordPress nonces, and other data visible only to logged-in administrators or other users.

CVSS v3
5.3
EG Score
5.3(medium)
EPSS
19.2%
KEV
Not listed

Published

May 29, 2026

Last Modified

May 29, 2026

Vendor Advisories for CVE-2026-2128(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 16× in last 7d / 72× 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 139 total refreshes for this CVE.

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

Frequently asked(5)

What is CVE-2026-2128?
CVE-2026-2128 is a medium vulnerability published on May 29, 2026. The Breeze plugin for WordPress is vulnerable to Exposure of Sensitive Information to an Unauthorized Actor in all versions up to, and including, 2.5.2 This is due to improper verification of the wordpressloggedin cookie in the inc/cache/execute-cache.php file when the "Cache Logged-in Users"…
When was CVE-2026-2128 disclosed?
CVE-2026-2128 was first published in the National Vulnerability Database on May 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-2128 actively exploited?
CVE-2026-2128 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 19.2% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-2128?
CVE-2026-2128 has a CVSS v3 base score of 5.3 (NVD).
How do I remediate CVE-2026-2128?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-2128, 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-2128

Explore →

Is Your Infrastructure Affected by CVE-2026-2128?

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