Skip to main content
VulnerabilityPublished

CVE-2026-129064: Nexter Blocks (WordPress plugin) · Missing Authorization

Affects Nexter Blocks (WordPress plugin)Source CVE Database V5

0
Compare

Not known to be exploited · CVSS 4.3 Medium : upgrade to 5.0.11 when convenient.

Data as of 17 Nov 2026, 22:49 UTC

CVSS 3.1 base score
4.3Medium
How severe the flaw is on the 0–10 CVSS scale.

Thin evidence

One scorer or none
CVSS scores by source
CNA (Patchstack)CVSS 3.14.3
Patch
Available – fixed in 5.0.11
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 17 Nov 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 17 Nov 2026.

What to do

Upgrade Nexter Blocks (WordPress plugin) to 5.0.11.

Affected software

ProductAffectedFixed in
Nexter Blocksthe-plus-addons-for-block-editorAffected
  • <5.0.11
Fixed in
  • 5.0.11

AI-suggested

A fix for this vulnerability is available in Nexter Blocks version 5.0.11. Users and administrators should upgrade to version 5.0.11 or later to remediate this issue. No additional mitigation actions are indicated by the vendor advisory.

Description

CVE-2026-129064 is a missing authorization vulnerability in POSIMYTH Innovations Nexter Blocks (the-plus-addons-for-block-editor) affecting versions prior to 5.0.11. This flaw allows exploitation of incorrectly configured access control security levels, potentially leading to unauthorized actions with limited privileges. The issue has a medium severity with a CVSS score of 4.3 and was fixed in version 5.0.11.

References

Community reviews

Loading reviews…