# 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.

- **Severity:** Medium 4.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** No
- **Published:** 24 Jun 2026
- **Updated:** 29 Jun 2026
- **Also known as:** GHSA-wqmq-jxx2-fmqp

## 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 (Exposure of Sensitive Information to an Unauthorized Actor)

## 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.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-9183 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-9183 in the wild and no public exploit code.

Affected product: 24liveblog – live blog tool. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-9183/ (Markdown: https://insights.sbomify.com/CVE-2026-9183/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-9183
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-9183
- OSV: https://osv.dev/vulnerability/CVE-2026-9183

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-9183/
Summaries are generated and may contain mistakes; the official description above is the record.