Skip to main content

Nexter Blocks CVE-2025-15678

| EUVDEUVD-2025-210624 MEDIUM
Cross-site Scripting (XSS) (CWE-79)
2026-08-06 WPScan GHSA-mg54-xc87-q8w3
6.1
CVSS 3.1 · Vendor: WPScan
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Recon
    Register or compromise WordPress Author account
  2. Delivery
    Craft SVG file with embedded JavaScript payload
  3. Exploit
    Upload malicious SVG via WordPress media library
  4. Install
    Deliver direct SVG URL to privileged victim
  5. C2
    Victim browser loads SVG and executes embedded script
  6. Execute
    Exfiltrate session token to attacker server
  7. Impact
    Hijack privileged WordPress session

Vulnerability Assessment

Weakness
CWE
MITRE ATT&CK

2 techniques across 2 tactics: Initial Access, Execution

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to possess a valid WordPress account with the upload_files capability - the Author role holds this by default. The victim (typically a higher-privileged user such as an Editor or Administrator) must access the uploaded SVG file via its direct URL in a browser; embedding the SVG via an <img> tag is insufficient for script execution in most modern browsers, but a direct URL request causes the browser to parse SVG as XML and execute inline scripts. Sites that disable file uploads for all roles below Editor, block SVG MIME types at the server or application layer, or that do not permit Author-level account registrations from untrusted users are not exploitable. The CVSS vector PR:N conflicts with the authentication requirement described - the actual exploitation condition is PR:L (authenticated, low-privilege account), which defenders should use when assessing realistic exposure.

Impact

The NVD CVSS 3.1 score of 6.1 (Medium) is assigned with PR:N, which directly contradicts the description stating exploitation requires a user 'able to upload files (Author by default)' - a clear authenticated precondition. This inflation of the apparent attack vector is a notable discrepancy; the corrected assessment with PR:L yields a lower effective severity. EPSS at 0.15% (5th percentile) confirms very low observed exploitation probability, and the vulnerability is absent from CISA KEV, meaning no confirmed active exploitation. The SSVC framework rates automatable as 'no' - consistent with the social-engineering step of directing a victim to load the SVG - and technical impact as 'partial,' appropriate for session-scoped XSS without direct server compromise. The public WPScan POC lowers the skill barrier to exploitation, making this a realistic threat specifically in multi-tenant WordPress environments, editorial platforms, or sites permitting Author-level registrations from untrusted parties. Against sites with tightly controlled Author accounts, real-world risk is substantially lower than the raw CVSS score implies.

Exploit ScenarioDerived

An attacker who holds or registers a WordPress Author account crafts an SVG file with an embedded <script> block that exfiltrates the victim's session cookie to an attacker-controlled endpoint. The attacker uploads the SVG through the WordPress media library and socially engineers a site administrator into clicking the direct SVG URL - for example, by embedding it in a support message or internal link. When the administrator's browser loads the SVG from the WordPress domain, the script executes same-origin, enabling session token theft and potential administrative account takeover. A public proof-of-concept for this technique is available via WPScan.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Aug 06, 2026

Stored Cross-Site Scripting in the Nexter Blocks WordPress plugin before 5.0.2 allows any authenticated user with file upload capability (Author role by default) to upload a malicious SVG file containing embedded JavaScript that executes in any victim's browser upon accessing the file. A publicly available proof-of-concept exists per WPScan, though EPSS at 0.15% (5th percentile) and absence from CISA KEV indicate low observed exploitation to date. The NVD-assigned CVSS PR:N conflicts with the description's clear authentication requirement - defenders should treat this as an authenticated vulnerability, which meaningfully narrows real-world exposure.

RemediationAI

Update the Nexter Blocks plugin to version 5.0.2 or later - this is the vendor-released patch that resolves the missing SVG sanitization, confirmed by WPScan and EUVD data. If immediate patching is not possible, restrict file upload capability for the Author role using a WordPress capability management plugin such as Members or User Role Editor to remove the upload_files capability from untrusted roles; note this will prevent Authors from uploading any media, breaking standard editorial workflows. Alternatively, block SVG MIME type uploads entirely by adding SVG to a blocked file-type list via a security plugin such as Wordfence or by modifying upload filters - this disables all SVG content site-wide. After patching or applying controls, audit the WordPress media library for existing SVG uploads and inspect their content for malicious <script> tags or event-handler attributes. See https://wpscan.com/vulnerability/2405c1ef-844a-462b-8329-c09d33b255b2/ for advisory details.

Affected VersionsENISA

Nexter Blocks 0 <5.0.2

Affected Packages

euvd nexter_blocks fix: 5.0.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

The vulnerability is rooted in CWE-79 (Improper Neutralization of Input During Web Page Generation - Cross-site Scripting), specifically the Stored variant. SVG files are XML-based graphics formats that natively support embedded JavaScript via inline <script> blocks and event-handler attributes (e.g., onload, onclick). WordPress itself restricts SVG uploads by default, but the Nexter Blocks plugin - a Gutenberg block library extending the WordPress block editor - overrides this restriction without applying content sanitization to the uploaded SVG. When WordPress serves the SVG directly as a static file, the browser parses and executes the embedded script in the context of the WordPress domain origin, enabling session theft, credential harvesting, or DOM manipulation against any user who accesses the file URL. The affected CPE is cpe:2.3:a:unknown:nexter_blocks:*:*:*:*:*:*:*:*, covering all versions below 5.0.2; the vendor field is listed as 'unknown' in NVD, indicating product attribution is not yet finalized.

Know when Nexter Blocks gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (WPScan) PRIMARY 6.1 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:N
vuln.today AI 5.4 MEDIUM

PR:L corrects NVD's PR:N since Author-level authentication is required to upload files; S:C and C:L/I:L reflect cross-user session impact via stored XSS.

3.1 AV:N/AC:L/PR:L/UI:R/S:C/C:L/I:L/A:N
4.0 AV:N/AC:L/AT:N/PR:L/UI:A/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (WPScan).

CVSS VectorVendor: WPScan

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Changed
Confidentiality
Low
Integrity
Low
Availability
None

Lifecycle Timeline

3
Patch available
Aug 06, 2026 - 07:02 EUVD
CVE Published
Aug 06, 2026 - 06:00 cve.org
UNKNOWN (no severity yet)
CVE Published
Aug 06, 2026 - 06:00 cve.org
MEDIUM 6.1

DescriptionCVE.org

The Nexter Blocks WordPress plugin before 5.0.2 does not sanitize uploaded SVG files and allows SVG uploads for any user able to upload files (Author by default), allowing them to upload a file containing malicious JavaScript that executes when the file is accessed, leading to Stored Cross-Site Scripting.

Threat Intelligence Overview

EPSS Score
0.2%
Top 95% exploitable
Prevalence
Medium
popular WordPress Gutenberg block builder plugin
Exploit
POC
Public exploit code exists
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC Yes
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
Poc
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

50
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +30
PoC: +20
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Cross-Site Scripting occurs when an application accepts untrusted data and sends it to a web browser without proper validation or encoding.

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy