dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-0726

HIGH · 8.1 CVSS v3.1 Published 2026-01-20
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The Nexter Extension – Site Enhancements Toolkit plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 4.4.6 via deserialization of untrusted input in the 'nxt_unserialize_replace' function. This makes it possible for unauthenticated attackers to inject a PHP Object. No known POP chain is present in the vulnerable software, which means this vulnerability has no impact unless another plugin or theme containing a POP chain is installed on the site. If a POP chain is present via an additional plugin or theme installed on the target system, it may allow the attacker to perform actions like delete arbitrary files, retrieve sensitive data, or execute code depending on the POP chain present.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The Nexter Extension – Site Enhancements Toolkit WordPress plugin (versions up to 4.4.6) is vulnerable to PHP Object Injection via the nxt_unserialize_replace function, which deserializes untrusted input without proper validation. This unauthenticated vulnerability cannot execute code on its own since no POP chain exists within the plugin; exploitation requires another installed plugin or theme containing a POP chain to achieve arbitrary code execution or file operations.

MitigationUpdate the plugin to the latest version once available; until then, audit all installed plugins and themes for POP chains, implement WAF rules to block deserialization functions, and remove unused plugins to reduce the attack surface.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
High
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Confirm plugin installation
    Check for the Nexter Extension plugin in the WordPress plugins directory (wp-content/plugins/) - look for a folder named 'nexter-extension' or similar naming convention containing the Site Enhancements Toolkit plugin.
    Affected if The plugin folder exists in the WordPress installation.
  2. Identify installed version
    Open the main plugin PHP file (typically the primary file in the plugin folder) and locate the version comment or version constant. Compare this version number against the affected range (versions up to and including 4.4.6).
    Affected if The installed version is 4.4.6 or lower.
  3. Verify plugin is active
    Check the WordPress site options table (wp_options) for the active_plugins option, or use the WordPress admin interface to confirm the plugin status. The nxt_unserialize_replace function must be loaded for the vulnerability to be reachable.
    Affected if The plugin is currently active on the WordPress site.
  4. Inspect for the vulnerable function
    Search the plugin files for the presence of the nxt_unserialize_replace function. This function deserializes input without validation. If found, the code path leading to it should be examined for unauthenticated access.
    Affected if The nxt_unserialize_replace function exists and can be reached without authentication.
  5. Audit other plugins for POP chains
    Review all installed plugins and themes for known PHP object injection POP chains. Since this vulnerability requires a separate plugin/theme with a POP chain to achieve code execution, enumerate all active plugins and cross-reference with known POP chain vulnerabilities.
    Affected if Any installed plugin or theme contains a POP chain that can be triggered via this deserialization vulnerability.

You are affected if the Nexter Extension Site Enhancements Toolkit plugin versions 4.4.6 or lower is installed and active, and a plugin or theme with a PHP object injection POP chain is present on the same WordPress installation.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Update the plugin to the latest version once available; until then, audit all installed plugins and themes for POP chains, implement WAF rules to block deserialization functions, and remove unused plugins to reduce the attack surface.

Recommended fix High confidence

Plugin version greater than 4.4.6 (check WordPress plugin repository for latest stable release)

  1. Navigate to the WordPress admin dashboard
  2. Go to Plugins > Installed Plugins
  3. Locate 'The Nexter Extension – Site Enhancements Toolkit' (also known as Nexter Theme or Nexter Extension)
  4. Check the current installed version - if it is 4.4.6 or below, an update is needed
  5. Update the plugin to the latest version available in the WordPress plugin repository
  6. Verify the update was successful and the new version is installed

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,970
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-0726 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-0726 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data