dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-49072

CRITICAL · 9.8 CVSS v3.1 Published 2025-06-06
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 AncoraThemes Mr. Murphy mr-murphy allows Object Injection.This issue affects Mr. Murphy: from n/a through < 1.2.12.1.

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 vulnerability in the Mr. Murphy WordPress theme allows attackers to inject arbitrary PHP objects by passing unsanitized data to the unserialize() function. This object injection can be chained with magic methods present in the theme or installed plugins to achieve remote code execution.

MitigationUpdate Mr. Murphy theme to version 1.2.12.1 or later to obtain the security patch that properly sanitizes deserialized data, or disable the theme if an update is unavailable.

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 if Mr. Murphy theme is installed
    Inspect the WordPress themes directory at wp-content/themes/ and check for a folder named 'mr-murphy', 'mr-murphy-theme', or similar naming convention. Alternatively, query the WordPress database in the wp_options table for the current active theme template value.
    Affected if The Mr. Murphy theme folder exists in the themes directory or is listed as the active theme in WordPress options.
  2. Determine the installed theme version
    Open the theme's style.css file located in the Mr. Murphy theme folder and locate the 'Version:' header in the file comment block at the top. Alternatively, check functions.php for a version constant or variable.
    Affected if The version number displayed is lower than 1.2.12.1.
  3. Compare against the patched version
    Take the version number found in step 2 and compare it numerically to version 1.2.12.1. Note that version numbers like 1.2.12, 1.2.11, or any 1.2.x version below 1.2.12.1 are considered vulnerable.
    Affected if The installed version is 1.2.12.1 or below, meaning the security patch is not applied.
  4. Inspect for vulnerable deserialization code
    Search theme PHP files for instances of unserialize() function calls. Specifically examine files that handle request parameters or AJAX handlers. Look for patterns like unserialize($_POST['...']) or unserialize($_GET['...']) without prior sanitization.
    Affected if The theme contains unserialize() calls that accept input from user-supplied parameters without sanitization.
  5. Check for active plugins with magic methods
    Review installed WordPress plugins for classes that contain magic methods such as __wakeup(), __destruct(), or __toString(). These methods could be chained with the deserialization flaw for code execution. List all active plugins via WordPress admin or wp_plugins table.
    Affected if Any installed plugin contains exploitable magic methods that could be triggered via PHP object injection.

You are affected if the Mr. Murphy theme is installed and its version is 1.2.12.1 or lower, especially if the theme contains 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.

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

Update Mr. Murphy theme to version 1.2.12.1 or later to obtain the security patch that properly sanitizes deserialized data, or disable the theme if an update is unavailable.

Recommended fix Moderate confidence

1.2.12.1

  1. Backup your WordPress site before making any changes
  2. Navigate to Dashboard > Appearance > Themes
  3. Locate the Mr. Murphy theme and update to version 1.2.12.1 or the latest available version
  4. After updating, verify the theme version is 1.2.12.1 or later in Themes panel
  5. Clear any caching plugins if enabled and test site functionality

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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