CVE-2026-9183
The 24liveblog - live blog tool plugin for WordPress is vulnerable …
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.
What to do now
- Check your exposureFind out whether the affected software runs anywhere in your environment, including systems of suppliers.
- UpdateInstall the version in which the vendor fixed the vulnerability. The references lead to the advisory.
- Set the orderSystems that can be reached from the internet come first, then the rest.
References
- plugins.trac.wordpress.org/browser/24liveblog/trunk/src/init.php#L139
- plugins.trac.wordpress.org/browser/24liveblog/trunk/src/init.php#L157
- www.wordfence.com/threat-intel/vulnerabilities/id/ceaccdb3-4d98-4463-9db9-a6f1712d6869?sou
- nvd.nist.gov/vuln/detail/CVE-2026-9183
- cve.org/CVERecord?id=CVE-2026-9183
Data: CVE list and the NVD. This product uses data from the NVD API but is not endorsed or certified by the NVD.