dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-24779

HIGH · 8.8 CVSS v3.1 Published 2025-07-16
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
Remotely reachable 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 NooTheme Yogi yogi allows Object Injection.This issue affects Yogi: from n/a through < 2.9.3.

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 NooTheme Yogi WordPress theme plugin contains a deserialization vulnerability where untrusted data is passed to PHP's unserialize() function without proper sanitization. This allows attackers to inject malicious PHP objects, potentially leading to remote code execution through object gadget chains available in the application or associated plugins.

MitigationUpdate the Yogi theme to version 2.9.3 or later to apply the vendor patch. If immediate update is not possible, disable the theme until the patch can be applied.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Yogi theme is installed
    In WordPress admin, go to Appearance > Themes to list all installed themes. Look for 'Yogi' or 'NooTheme Yogi' in the list.
    Affected if The Yogi theme by NooTheme appears in the installed themes list, regardless of whether it is active.
  2. Identify the installed Yogi theme version
    In WordPress admin, click on the Yogi theme to view its details. The version number is displayed in the theme description or footer area. Alternatively, check the style.css file in wp-content/themes/yogi/ for the 'Version:' comment header.
    Affected if The version displayed is below 2.9.3 (the patched version).
  3. Verify the theme contains deserialization code
    Using a file search or code editor, examine PHP files in the Yogi theme directory for calls to unserialize() on input data. Search for patterns like 'unserialize($_POST', 'unserialize($_GET', 'unserialize($_REQUEST', or 'unserialize($' without proper sanitization functions like sanitize_text_field.
    Affected if Theme PHP files contain unserialize() calls that process raw input from HTTP request parameters without validation.
  4. Check for exposed entry points
    Inspect AJAX action handlers and shortcode callback functions in the theme's inc/, includes/, or shortcodes/ directories. Look for functions that accept user input and pass it to unserialize(). Common patterns include add_action('wp_ajax_*' or add_shortcode.
    Affected if The theme exposes AJAX handlers or shortcodes that accept and unserialize user-submitted data without validation.
  5. Confirm the theme is active
    In WordPress admin > Appearance > Themes, verify whether the Yogi theme is the currently active theme.
    Affected if The Yogi theme is actively running on the WordPress site, making the deserialization vulnerability exploitable.

If the Yogi theme is installed with a version below 2.9.3 and contains PHP files with unserialize() calls processing untrusted input, the environment is affected by this CVE.

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 Yogi theme to version 2.9.3 or later to apply the vendor patch. If immediate update is not possible, disable the theme until the patch can be applied.

Recommended fix Moderate confidence

Upgrade to Yogi version 2.9.3 or later

  1. 1. Backup your WordPress site database and files before making any changes
  2. 2. Navigate to the WordPress admin dashboard
  3. 3. Go to Plugins (or Appearance > Themes if this is a theme)
  4. 4. Locate the Yogi plugin/theme by NooTheme
  5. 5. Check the current installed version to confirm it is below 2.9.3
  6. 6. If an update is available, click 'Update Now' to upgrade to version 2.9.3 or later
  7. 7. If no automatic update is available, manually download version 2.9.3 or latest from the vendor
  8. 8. Deactivate the current Yogi plugin/theme

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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