CVE-2026-17011

Nexter Blocks < 5.0.2 - Contributor+ Stored CSS Injection

Published Aug 9, 2026 CVSS 3.1 · 3.8 Low EPSS < 1% KEV · Not listed
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.

Analysis

AI-generated

Technical impact

The Nexter Blocks WordPress plugin version prior to 5.0.2 fails to enforce permission checks on a REST endpoint that saves global CSS, allowing users with Contributor privileges to inject arbitrary CSS that is rendered site‑wide. This client‑side injection can deface the site, conceal content, or manipulate the user interface, effectively giving attackers control over the visual presentation of the site. The weakness is a stored CSS injection flaw (CWE‑784) and involves external control of system configuration via a REST endpoint (CWE‑345).

Affected Systems

All WordPress sites running Nexter Blocks before version 5.0.2 are affected when a user has Contributor or higher privileges. The vulnerability applies to any environment where the plugin’s REST API is exposed and the Contributor role can be assigned, regardless of the specific WordPress theme or other plugins.

Risk and Exploitability

The CVSS score is 3.8, the EPSS score is < 1%, and the issue is not present in CISA’s KEV catalog. The likely attack vector requires an attacker to possess or compromise a Contributor account on the affected site, after which they can send a crafted request to the vulnerable endpoint to store malicious CSS. Attackers who gain such access can permanently modify the site’s appearance and potentially hide or alter content. Because the flaw is client‑side, remote code execution is not possible, but the impact on user experience and the potential for defacement make this a serious concern for sites that allow Contributor permissions.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade Nexter Blocks to version 5.0.2 or later, which enforces proper permission checks on the global CSS endpoint.
  • If an upgrade is not immediately possible, restrict Contributor role capabilities to remove the ability to edit global CSS or use a capability‑managing plugin to revoke this function.
  • Configure a web application firewall or security‑plugin rule to block or sanitize requests to the vulnerable REST endpoint, preventing the injection of malicious CSS until a patch is applied.

Generated by OpenCVE AI on August 13, 2026 at 09:22 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
First Time appeared Wordpress-extensions
Wordpress-extensions nexter Blocks
Vendors & Products Wordpress-extensions
Wordpress-extensions nexter Blocks
Type Values Removed Values Added
Weaknesses CWE-345
Metrics cvssV3_1

{'score': 3.8, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:U/C:N/I:L/A:L'}

ssvc

{'options': {'Automatable': 'no', 'Exploitation': 'none', 'Technical Impact': 'partial'}, 'version': '2.0.3'}

Type Values Removed Values Added
Weaknesses CWE-784
Type Values Removed Values Added
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.
Title Nexter Blocks < 5.0.2 - Contributor+ Stored CSS Injection
References
Weaknesses
  • CWE-345

    Insufficient Verification of Data Authenticity

  • CWE-784

    Reliance on Cookies without Validation and Integrity Checking in a Security Decision

Sources

Status
PUBLISHED
Assigner
WPScan
Published
Updated
Aug 11, 2026, 7:47 PM
Reserved
Jul 24, 2026, 10:10 AM
Status
Deferred
Published
Aug 9, 2026, 6:18 AM
Modified
Aug 26, 2026, 4:31 PM