CVE-2026-17011: Nexter Blocks (WordPress plugin) · Insufficient Verification of Data Authenticity
Affects Nexter Blocks (WordPress plugin)Source CVE Database V5
Not known to be exploited · CVSS 3.8 Low : upgrade to 5.0.2 when convenient.
Data as of 8 Nov 2026, 23:24 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 6% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 5.0.2
CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:LExploitation evidence
Disclosed: evidence found.
CVE published 9 Aug 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 8 Nov 2026.
What to do
Upgrade Nexter Blocks (WordPress plugin) to 5.0.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Nexter Blocks | Affected
| Fixed in
|
AI-suggested
If you cannot patch yet, restrict Contributor role permissions or monitor and control access to REST endpoints that allow saving global CSS.
Description
The Nexter Blocks WordPress plugin before 5.0.2 does not restrict who can save global CSS through one of its REST endpoints, allowing users with at least the Contributor role to store arbitrary CSS that is rendered site-wide on the front end, enabling defacement, content hiding, and UI redressing.