CVE-2026-9183: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in 24liveblog 24liveblog – live blog tool
The 24liveblog - live blog tool plugin for WordPress is vulnerable to Exposure of Sensitive Information in versions up to, and including, 2.2. This is due to the lb24_block_enqueue_scripts() function being hooked to enqueue_block_editor_assets and, for any non-administrator user, falling back to loading the administrator-configured site-wide 24liveblog integration secrets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the options table via get_option() and emitting them through wp_localize_script() as the lb24BlockData JavaScript object. This makes it possible for authenticated attackers, with contributor-level access and above, to extract third-party 24liveblog account credentials (including the API token and refresh token) by simply opening the block editor and inspecting the page source.
AI Analysis
Technical Summary
CVE-2026-9183 describes an information exposure vulnerability in the 24liveblog WordPress plugin (versions up to and including 2.2). The vulnerability arises from the lb24_block_enqueue_scripts() function, which is hooked to enqueue_block_editor_assets. For non-administrator users, this function loads sensitive 24liveblog integration secrets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the WordPress options table and exposes them through wp_localize_script() as the lb24BlockData JavaScript object. Consequently, any authenticated user with contributor-level permissions or higher can extract these third-party account credentials by opening the block editor and inspecting the page source.
Potential Impact
An attacker with contributor-level access or higher can obtain sensitive third-party 24liveblog account credentials, including API tokens and refresh tokens. This exposure could potentially allow unauthorized access to the 24liveblog service associated with the compromised credentials. The vulnerability does not impact confidentiality beyond credential exposure, nor does it affect integrity or availability directly.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict contributor-level access to trusted users only and avoid using the vulnerable plugin version. Monitor official 24liveblog or WordPress plugin sources for updates or patches addressing this issue.
CVE-2026-9183: CWE-200 Exposure of Sensitive Information to an Unauthorized Actor in 24liveblog 24liveblog – live blog tool
Description
The 24liveblog - live blog tool plugin for WordPress is vulnerable to Exposure of Sensitive Information in versions up to, and including, 2.2. This is due to the lb24_block_enqueue_scripts() function being hooked to enqueue_block_editor_assets and, for any non-administrator user, falling back to loading the administrator-configured site-wide 24liveblog integration secrets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the options table via get_option() and emitting them through wp_localize_script() as the lb24BlockData JavaScript object. This makes it possible for authenticated attackers, with contributor-level access and above, to extract third-party 24liveblog account credentials (including the API token and refresh token) by simply opening the block editor and inspecting the page source.
CVSS v3.1
Score 4.3medium
Affected software
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
CVE-2026-9183 describes an information exposure vulnerability in the 24liveblog WordPress plugin (versions up to and including 2.2). The vulnerability arises from the lb24_block_enqueue_scripts() function, which is hooked to enqueue_block_editor_assets. For non-administrator users, this function loads sensitive 24liveblog integration secrets (lb24_token, lb24_refresh_token, lb24_uid, lb24_uname) from the WordPress options table and exposes them through wp_localize_script() as the lb24BlockData JavaScript object. Consequently, any authenticated user with contributor-level permissions or higher can extract these third-party account credentials by opening the block editor and inspecting the page source.
Potential Impact
An attacker with contributor-level access or higher can obtain sensitive third-party 24liveblog account credentials, including API tokens and refresh tokens. This exposure could potentially allow unauthorized access to the 24liveblog service associated with the compromised credentials. The vulnerability does not impact confidentiality beyond credential exposure, nor does it affect integrity or availability directly.
Mitigation Recommendations
Patch status is not yet confirmed — check the vendor advisory for current remediation guidance. Until a fix is available, restrict contributor-level access to trusted users only and avoid using the vulnerable plugin version. Monitor official 24liveblog or WordPress plugin sources for updates or patches addressing this issue.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- Wordfence
- Date Reserved
- 2026-05-21T14:54:43.626Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a3b7813eed863c81e5f7319
Added to database: 06/24/2026, 06:24:19 UTC
Last enriched: 07/01/2026, 22:17:43 UTC
Last updated: 08/06/2026, 19:30:51 UTC
Views: 49
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.