LiveActive security incident?Get immediate response
CVE Record

CVE-2026-25429: WordPress Nexa Blocks plugin <= 1.1.1 - PHP Object Injection vulnerability

Deserialization of Untrusted Data vulnerability in wpdive Nexa Blocks nexa-blocks allows Object Injection.This issue affects Nexa Blocks: from n/a through <= 1.1.1.

CriticalCVSS 9.8Not KEV-listedUpdated
Glexia's TakeAutomated analysiscritical

Security readout for executives and security teams

Plain-English summary

CVE-2026-25429 is a critical vulnerability in the WordPress Nexa Blocks plugin. Sites using Nexa Blocks version 1.1.1 or earlier may be exposed to unsafe PHP object handling. The public record rates it highly severe, but the provided sources do not confirm active exploitation or name a fixed version.

Executive priority

Treat this as urgent for any organization using Nexa Blocks on public WordPress sites. The vulnerability is rated critical and requires no authentication, but current sources do not confirm exploitation or a patch. Focus on rapid inventory, exposure reduction, and vendor-guided remediation.

Technical view

The issue is CWE-502, deserialization of untrusted data, allowing PHP object injection in wpdive Nexa Blocks through version 1.1.1. The CVSS 3.1 score is 9.8 with network access, low complexity, no privileges, and no user interaction required. Impact is rated high for confidentiality, integrity, and availability.

Likely exposure

Exposure is likely limited to WordPress installations with the Nexa Blocks plugin installed, especially public-facing sites running version 1.1.1 or earlier. The provided data does not identify other affected products or platforms.

Exploitation context

The CVE is not listed as KEV in the supplied data, and no cited source confirms active exploitation. Risk remains high because the CVSS vector describes remote, unauthenticated exploitation with no user interaction and high potential impact.

Researcher notes

Public details are limited. The record identifies unsafe deserialization and PHP object injection but does not provide vulnerable code paths, parameters, proof-of-concept details, exploitation evidence, or a confirmed fixed version in the supplied sources.

Mitigation direction

  • Inventory WordPress sites for the Nexa Blocks plugin.
  • Check installed Nexa Blocks versions against 1.1.1 or earlier.
  • Review vendor and Patchstack guidance for fixed versions or official mitigations.
  • If acceptable, deactivate or remove the plugin until remediation is confirmed.
  • Prioritize public-facing and business-critical WordPress sites first.

Validation and detection

  • Confirm whether Nexa Blocks is installed on each WordPress site.
  • Record plugin version and compare with the affected range.
  • Verify whether a vendor-fixed version is available before upgrading.
  • Check web logs and security alerts for unusual plugin-related activity.
  • Document remediation status for each affected WordPress instance.
Prepared
Confidence
medium
Sources
3

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-502: Code execution behavior lookup

Code execution and unsafe deserialization weaknesses often justify reviewing execution behavior and process 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
cve · low confidence lookup

CVE-2026-25429 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
Critical
CVSS
9.8 (3.1)
Known Exploited
No
Published

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

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
0Timeline events
0ADP providers
2Source links

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
9.8CVSS 3.1CriticalCVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H3.95.9Primary CVE score

Vulnerability scoring details

Base CVSS 3.1 score

9.8Critical
CVSS 3.1 vector shape for CVE-2026-25429Attack VectorAttack ComplexityPrivileges RequiredUser InteractionScopeConfidentiality ImpactIntegrity ImpactAvailability Impact

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

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

Products and packages named in the record

VendorProductVersion / packageStatus
wpdiveNexa Blocksnexa-blocks, 0unaffected
Weakness

CWE details

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

CWE-502 · source CWE mapping

Deserialization of Untrusted Data

Deserialization of Untrusted Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.