EUVD-2026-38681
GHSA-wqmq-jxx2-fmqp
Severity by source
AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
AV:N because block editor is web-accessible; PR:L because contributor-level WordPress authentication is required; C:L because only scoped third-party service tokens are exposed, not broader system data.
Primary rating from Vendor (Wordfence).
CVSS VectorVendor: Wordfence
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N
Lifecycle Timeline
2DescriptionCVE.org
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.
AnalysisAI
Authenticated information disclosure in the 24liveblog WordPress plugin (versions ≤ 2.2) exposes third-party API credentials - including OAuth access tokens, refresh tokens, account UIDs, and usernames - to any contributor-level WordPress user who opens the block editor. The plugin's lb24_block_enqueue_scripts() function, hooked to enqueue_block_editor_assets, retrieves administrator-configured integration secrets from the WordPress options table and renders them into the page as a JavaScript global object (lb24BlockData) for all non-administrator users, where they are readable via basic browser source inspection. …
Unlock full vulnerability intelligence
- Risk assessment & exploitation conditions
- Attack chain visualization
- Remediation with exact patch versions
- Threat intelligence from 22 sources
- Personal watchlist & email alerts
Free forever · No credit card required
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata
Vulnerability AssessmentAI
| Exploitation | Exploitation requires an authenticated WordPress user account at Contributor level or above (confirmed by PR:L in the CVSS:3.1/AV:N/AC:L/PR:L/UI:N vector). … Additional conditions and limiting factors are described in the full assessment. |
| Risk Assessment | The CVSS 3.1 base score of 4.3 (AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N) is technically accurate per scoring guidelines but qualitatively undersells the impact in configured deployments: the exposed data includes OAuth bearer tokens and refresh tokens for the 24liveblog service, which could enable an attacker to fully impersonate the site's live blogging account, manipulate published live blog content, or harvest associated audience data - impacts not captured by C:L. … Full risk analysis with EPSS, KEV, and SSVC signal comparison available after sign-in. |
| Exploit Scenario | An attacker who holds or compromises a contributor-level WordPress account on a target site navigates to the block editor by creating a new draft post, then opens browser developer tools and inspects the page source or evaluates lb24BlockData in the JavaScript console, retrieving the site's 24liveblog API token, refresh token, UID, and username in plaintext. No exploit tooling is required; the entire attack is completable in under a minute using standard browser functionality. … |
| Remediation | No vendor-released patched version has been independently confirmed in the available intelligence data. … Detailed patch versions, workarounds, and compensating controls in full report. |
Threat intelligence, references, and detailed analysis are available after sign-in.
More in 24Liveblog Live Blog Tool
View allSame weakness CWE-200 – Information Exposure
View allSame technique Information Disclosure
View allShare
External POC / Exploit Code
Leaving vuln.today