Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-2128 medium CVSS 5.3

Information Disclosure in Breeze (WordPress plugin) (CVE-2026-2128)

Summary

Vulnerability in Breeze (WordPress plugin) (CVE-2026-2128). Risk of unauthorized operations or information disclosure. Exploitable via wordpress_logged_in_.

Original description

The description as published by the source.

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.

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-2128 has been found in Breeze (WordPress plugin).
Attackers can target a specific entry point like wordpress_logged_in_ over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: apply the vendor's official patched release.
If unsure, ask your IT team or search "Breeze (WordPress plugin) CVE-2026-2128" on the vendor's site.

CVE-2026-2128 (Breeze (WordPress plugin)) — CWE-200 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: wordpress_logged_in_
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

Information disclosure (CWE-200) exists in Breeze (WordPress plugin). Attackers reach the vulnerable code path via wordpress_logged_in_ without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of Breeze (WordPress plugin). Attack surface: wordpress_logged_in_.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to the patched release per vendor advisory.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Audit SBOM/dependencies to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    Audit SBOM/dependencies for affected components.

    資産台帳・SBOM・依存マニフェストで Breeze (WordPress plugin) を使っているサービスとバージョンを洗い出す。

  2. 2
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details