Is 24liveblog safe to use?

Laskyr does not give safety verdicts. 24liveblog is closed on wordpress.org. Closed on 2026-06-18 (reason given: Security Issue). Closed plugins get no updates through WordPress, so new security holes will not be fixed for you. Keep 24liveblog on the latest version and remove it if you do not use it.

Which versions of 24liveblog are vulnerable?

Known issues on record (newest first): Information disclosure (2.2 and older); Missing authorization check (2.2 and older). The full list with sources is on this page.

What should I do if my 24liveblog is out of date?

Take a backup, then update it from Dashboard > Updates (or run wp plugin update 24liveblog). If you cannot update right away, deactivate it until you can. If you think the site was already attacked, run a free scan at https://laskyr.com/scan.

Plugins · 24liveblog · data as of 2026-11-04

Is 24liveblog safe? Known vulnerabilities and latest version

Status: Closed 2026-06-18
Known issues on record: 2
Unpatched in latest: 0

What to do

Replace it. A closed plugin gets no updates through WordPress, so any hole found from now on stays open.
Deactivate and delete it once you have a replacement (Plugins → Deactivate → Delete). Deleting removes its files; deactivating alone leaves them on the server.
If you ran a vulnerable version and something looks off (spam pages, strange admins, redirects), run the free scan, or have us clean it: Emergency Cleanup, $499.

With WP-CLI, once you have a replacement: wp plugin deactivate 24liveblog && wp plugin delete 24liveblog

Check your version

Known vulnerabilities

2 on record, newest first. “Affected” is the version range the source gives; “fixed in” is the version the source names, or (marked *) the first wordpress.org release after the last affected version. 2 record(s) do not state which versions are affected.

medium 4.3 CVE-2026-9183 · published 2026-06-24

Information disclosure in 24liveblog (2.2 and older)

Affected: 2.2 and older
Fixed in: unknown
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

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.

NVD CVE-2026-9183 Wordfence advisory Plugin source

medium 4.3 CVE-2026-9184 · published 2026-06-24

Missing authorization check in 24liveblog (2.2 and older)

Affected: 2.2 and older
Fixed in: unknown
Access needed (per CVSS): Needs a low-level account (e.g. subscriber)
Range from: CVE record (the advisory publisher) · score by Wordfence

Details from the advisory

The 24liveblog - live blog tool plugin for WordPress is vulnerable to unauthorized modification of data due to a missing capability check on the update_lb24_token() AJAX function in versions up to, and including, 2.2. The handler only verifies the 'lb24' nonce (which is generated and localized to any user with block editor access via lb24_block_enqueue_scripts()) and does not verify the user's capabilities or that the supplied user_id belongs to the current user. This makes it possible for authenticated attackers, with author-level access and above, to overwrite the lb24_token, lb24_uid, lb24_refresh_token, and lb24_uname user meta values of any user (including administrators) as well as the corresponding site-wide options, effectively hijacking the plugin's integration with the 24liveblog service.

NVD CVE-2026-9184 Wordfence advisory Plugin source

Recent activity

2026-06-18 — closed on wordpress.org (Security Issue).
2026-06-24 — Information disclosure disclosed (CVE-2026-9183), fix version not stated.
2026-06-24 — Missing authorization check disclosed (CVE-2026-9184), fix version not stated.

Free. We check the CVE feeds every day and email you only when a new issue for 24liveblog (24liveblog) is published or a fix ships. Unsubscribe in one click.

Browse vulnerabilities

Types found in this plugin: Sensitive data exposure (1) · Missing authorization (1)

Where this data comes from

Version, last update, installs, closure: wordpress.org/plugins/24liveblog (Plugins API), fetched 2026-11-04.
Vulnerabilities: NIST National Vulnerability Database (NVD), checked 2026-11-04. This product uses data from the NVD API but is not endorsed or certified by the NVD.
Each record links to its CVE page and to the original advisory (Wordfence, Patchstack or WPScan) where there is one. We only list a CVE here when its references or its advisory name this exact plugin, so a few real issues may be missing; none should be about a different plugin. Spot an error? Email Daniel.

Badge for your site or docs (states facts with a date, not a verdict):

<a href="https://laskyr.com/plugins/24liveblog"><img src="https://laskyr.com/plugins/24liveblog/badge.svg" alt="24liveblog vulnerability status"></a>

← Check another plugin · Free hacked-site scan