dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2026-39529

CRITICAL · 9.8 CVSS v3.1 Published 2026-06-17
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/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
Unauthenticated PHP Object Injection in Elementra <= 1.0.9 versions.

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

This is an unauthenticated PHP Object Injection vulnerability in the Elementra theme/plugin for versions 1.0.9 and below. The flaw allows remote attackers to inject malicious PHP objects into the application's deserialization process without authentication, potentially leading to remote code execution.

MitigationUpgrade Elementra to a version newer than 1.0.9, or if no update exists, sanitize all user input before passing to PHP's unserialize() function and implement proper access controls on vulnerable endpoints.

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
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/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. Identify Elementra version
    Locate the Elementra theme/plugin files and check the version in the main PHP file (typically header, main class, or version config). Common locations: elementra.php, class-elementra.php, or version.php within the plugin/theme directory.
    Affected if Installed version is 1.0.9 or lower
  2. Find deserialization usage
    Search the Elementra plugin/theme directory for calls to PHP's unserialize() function. Use grep or similar: grep -r "unserialize" /path/to/elementra/
    Affected if Code contains unserialize() calls processing external or user-supplied data
  3. Identify endpoint exposure
    Examine PHP files that contain unserialize() calls and check if they are accessible via direct URL access (not admin-only). Look for files in the root or ajax directories.
    Affected if Deserialization code is accessible without authentication (no login/capability checks)
  4. Check input source
    Review the unserialize() calls found and trace whether the data being deserialized comes from $_GET, $_POST, $_REQUEST, or HTTP headers without sanitization.
    Affected if User-controlled input is passed directly to unserialize() without validation

You are affected if Elementra version is 1.0.9 or below AND the plugin/theme contains unauthenticated unserialize() calls processing user input.

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.

From vendor data
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade Elementra to a version newer than 1.0.9, or if no update exists, sanitize all user input before passing to PHP's unserialize() function and implement proper access controls on vulnerable endpoints.

Have this fixed Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-39529 — 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-39529 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