# CVE-2026-24377: WordPress Nexter Blocks plugin <= 4.6.3 - Sensitive Data Exposure vulnerability

> An attacker can retrieve embedded sensitive system data from the Nexter Blocks WordPress plugin, potentially exposing internal configuration details.

- **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:** 22 Jan 2026
- **Updated:** 28 Apr 2026
- **Also known as:** GHSA-mqq6-2252-927j

## What is CVE-2026-24377?

CVE-2026-24377 is a medium-severity vulnerability in POSIMYTH Nexter Blocks, published on 22 Jan 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

Exposure of Sensitive System Information to an Unauthorized Control Sphere vulnerability in POSIMYTH Nexter Blocks the-plus-addons-for-block-editor allows Retrieve Embedded Sensitive Data.This issue affects Nexter Blocks: from n/a through <= 4.6.3.

Weakness: CWE-497 (Exposure of Sensitive System Information to an Unauthorized Control Sphere)

## Which versions are affected by CVE-2026-24377?


## How do I fix CVE-2026-24377?

No fix has been published for CVE-2026-24377 yet. Limit exposure of the affected software until one is available.

## Is CVE-2026-24377 being exploited?

There is no known exploitation of CVE-2026-24377 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-24377 is a medium-severity vulnerability in POSIMYTH Nexter Blocks, published on 22 Jan 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-24377 in the wild and no public exploit code.

Affected product: POSIMYTH Nexter Blocks. 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-24377/ (Markdown: https://insights.sbomify.com/CVE-2026-24377/index.md)
```

## Sources

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

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