CVE-2026-9183 24liveblog <= 2.2 - Authenticated (Contributor+) Exposure of Sensitive Information via Block Editor Script Localization
Authenticated contributors can extract sensitive 24liveblog API credentials by inspecting the block editor page source due to improper script localization.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- None listed
What is CVE-2026-9183?
CVE-2026-9183 is a medium-severity vulnerability in 24liveblog – live blog tool, published on 24 Jun 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official 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.
Weakness: CWE-200
Which versions are affected by CVE-2026-9183?
How do I fix CVE-2026-9183?
No fix has been published for CVE-2026-9183 yet. Limit exposure of the affected software until one is available.
Is CVE-2026-9183 being exploited?
There is no known exploitation of CVE-2026-9183 in the wild and no public exploit code.
Sources
Also known as GHSA-wqmq-jxx2-fmqp.