LiveActive security incident?Get immediate response
CVE Record

CVE-2026-15420: Nexter Blocks <= 5.0.0 - Authenticated (Subscriber+) Path Traversal to Arbitrary CSS/JS File Deletion via 'plus_name' Parameter

The Nexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder plugin for WordPress is vulnerable to Directory Traversal in all versions up to, and including, 5.0.0 via the 'plus_name' parameter. This makes it possible for authenticated attackers, with subscriber-level access and above, to delete arbitrary JS/CSS files on the server, which can lead to denial of service or destruction of critical plugin and theme assets.

MediumCVSS 4.3Not KEV-listedUpdated
Glexia's TakeAutomated analysismoderate

Security readout for executives and security teams

Plain-English summary

An authenticated WordPress user with subscriber-level access or higher can abuse Nexter Blocks through version 5.0.0 to delete JavaScript or CSS files. Lost theme or plugin assets could disrupt site appearance or operation. The supplied evidence does not establish deletion of arbitrary non-JS/CSS files.

Executive priority

Prioritize prompt review on public or business-critical WordPress sites with subscriber accounts. This is not presented as an unauthenticated takeover, but inexpensive low-privilege abuse could damage site assets and create operational disruption. Preserve backups before remediation.

Technical view

CVE-2026-15420 is a CWE-22 path-traversal issue in the plugin's plus_name parameter. Network-accessible, low-privilege requests require no user interaction and may select JS/CSS files outside the intended directory for deletion. The supplied CVSS 3.1 score is 4.3, although its availability metric does not reflect the description's denial-of-service consequence.

Likely exposure

Exposure is likely where Nexter Blocks version 5.0.0 or earlier is installed and untrusted users hold subscriber-or-higher accounts. Risk increases when public registration or compromised low-privilege accounts provide access. The bundle's structured affected-version entry is inconsistent, so confirm applicability against current vendor guidance.

Exploitation context

The source bundle marks this CVE as absent from KEV and provides no evidence of active exploitation. Exploitation requires an authenticated subscriber-level or higher account, but reportedly needs neither elevated administrative privileges nor victim interaction.

Researcher notes

The narrative and title state that all versions through 5.0.0 are affected, while the structured affected entry lists version "0" and defaults others to unaffected. Treat the narrative range as provisional pending vendor confirmation. The referenced WordPress changeset may indicate remediation work, but the supplied material does not explicitly name a fixed version.

Mitigation direction

  • Check vendor guidance for the confirmed fixed release or supported mitigation.
  • Update to a vendor-confirmed non-vulnerable version when available.
  • Disable or remove the plugin if safe updating is unavailable.
  • Restrict or suspend unnecessary subscriber accounts and public registration.
  • Maintain tested backups of plugin, theme, and generated assets.

Validation and detection

  • Inventory all WordPress sites for Nexter Blocks and record installed versions.
  • Identify subscriber-or-higher accounts, especially unknown, dormant, or recently created users.
  • Compare plugin and theme JS/CSS files with trusted packages or backups.
  • Review application and security logs for suspicious plus_name requests or unexplained asset deletion.
  • Confirm the installed release is declared non-vulnerable by authoritative vendor guidance.
Prepared
Confidence
medium
Sources
5

Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.

Potential ATT&CK relevance

Conservative CVE-to-ATT&CK context

These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.

ATT&CK lookup starting points

Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.

cwe · medium confidence lookup

CWE-22: File access and web shell behavior lookup

File traversal and upload weaknesses can lead teams to review file, web shell, execution, and collection telemetry. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.

Open ATT&CK lookup
description · low confidence lookup

File access behavior lookup

The CVE wording references file access or upload behavior, so file telemetry and web shell review may help. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.

Open ATT&CK lookup
cve · low confidence lookup

CVE-2026-15420 mapping review

Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.

Open ATT&CK lookup
Vulnerability profileCVE Program record
Severity
Medium
CVSS
4.3 (3.1)
Known Exploited
No
Published

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Official CVE source material

CNA and ADP enrichment extracted from CVE v5

These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.

1CVSS vectors
5Timeline events
1ADP providers
5Source links

SSVC decision data

CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: partial

CVSS vector scores

1 official score

We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.

ScoreVersionSeverityVectorExploitImpactSource
4.3CVSS 3.1MediumCVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N2.81.4Wordfence

Vulnerability scoring details

Base CVSS 3.1 score

4.3Medium
CVSS 3.1 vector shape for CVE-2026-15420Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

Vector: CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:L/A:N

Attack Vector
NetworkAdjacentLocalPhysical
Attack Complexity
LowHigh
Privileges Required
NoneLowHigh
User Interaction
NoneRequired
Scope
ChangedUnchanged
Confidentiality Impact
HighLowNone
Integrity Impact
HighLowNone
Availability Impact
HighLowNone

Vulnerability timeline

Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.

  1. CVE reservedCVE Program

    The CVE ID was reserved by the assigning CNA.

  2. Source timelineWordfence

    Vendor Notified

  3. Source timelineWordfence

    Disclosed

  4. CVE publishedCVE Program

    The CVE record was published.

  5. CVE updatedCVE Program

    The CVE record metadata indicates this as the latest update time.

ADP provider summaries

CISA-ADPCISA ADP Vulnrichment
other:ssvc
Affected products

Products and packages named in the record

VendorProductVersion / packageStatus
posimyththemesNexter Blocks – Gutenberg Blocks, Page Builder & AI Website Builder0unaffected
Weakness

CWE details

CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.

CWE-22 · source CWE mapping

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal')

Improper Limitation of a Pathname to a Restricted Directory ('Path Traversal') represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.