dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-64206

CRITICAL · 9.8 CVSS v3.1 Published 2025-12-18
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
Deserialization of Untrusted Data vulnerability in TieLabs Jannah jannah allows Object Injection.This issue affects Jannah: from n/a through <= 7.6.0.

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

A deserialization of untrusted data vulnerability in the Jannah WordPress theme (versions up to 7.6.0) allows remote attackers to inject malicious PHP objects by manipulating serialized data processed by the application. This object injection can lead to remote code execution, file operations, or SQL injection depending on available gadget chains in the theme and installed plugins.

MitigationUpdate to a patched version of Jannah theme when available; if no patch exists, temporarily disable the theme and audit all deserialization entry points (unserialize() calls) to replace with safe alternatives like json_decode. Review installed plugins for exploitable PHP gadget chains.

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. Verify Jannah theme is installed
    Check WordPress admin under Appearance > Themes or inspect wp-content/themes/ directory for the jannah folder. Also query the wp_options table for 'template' or 'stylesheet' values containing 'jannah'.
    Affected if The jannah theme folder exists in wp-content/themes/ or the theme is set as active in WordPress options.
  2. Determine installed Jannah theme version
    Open the style.css file in wp-content/themes/jannah/ and read the 'Version:' header field. Alternatively, query the wp_options table for theme version metadata if stored there.
    Affected if The reported version is 7.6.0 or any earlier version, since the vulnerability affects versions up to 7.6.0.
  3. Locate deserialization code in theme files
    Search all PHP files in wp-content/themes/jannah/ for calls to unserialize() function. Use grep or similar: grep -r "unserialize" wp-content/themes/jannah/
    Affected if Any unserialize() call exists in the theme's PHP files, particularly in files that process request parameters or stored data.
  4. Identify if user input reaches unserialize
    Review the unserialize() calls found to determine if they process data from $_GET, $_POST, $_COOKIE, or database values that could be manipulated by an attacker. Check function call arguments for any user-controllable source.
    Affected if Unserialize is called on data derived from HTTP request parameters, cookies, or external input sources without prior validation.
  5. Check for exposed attack surface
    Identify which theme files contain the vulnerable unserialize calls and determine if they are accessible via direct URL access (front-end PHP files). Review AJAX handlers and template files that process serialized data.
    Affected if Vulnerable unserialize code is in publicly accessible files or AJAX endpoints that can be reached without authentication.

A user is affected if the Jannah theme version is 7.6.0 or earlier AND the theme contains unserialize() calls that process untrusted user input without validation.

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

Update to a patched version of Jannah theme when available; if no patch exists, temporarily disable the theme and audit all deserialization entry points (unserialize() calls) to replace with safe alternatives like json_decode. Review installed plugins for exploitable PHP gadget chains.

Have this fixed Scoped from the published advisory
  • Consultation8.0 h
  • Implementation24.0 h
  • Testing12.0 h
  • Review / QA6.0 h
50.0 hours of engineering $8,800
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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