dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-31074

HIGH · 8.8 CVSS v3.1 Published 2025-04-01
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 MDJM Mobile DJ Manager mobile-dj-manager allows Object Injection.This issue affects Mobile DJ Manager: from n/a through <= 1.7.5.2.

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

PHP Object Injection vulnerability in the Mobile DJ Manager WordPress plugin allows remote attackers to deserialize untrusted data, potentially leading to remote code execution if suitable gadget chains exist in the application or included libraries. The vulnerability stems from unsafe use of PHP's unserialize() function on user-controlled input.

MitigationUpdate Mobile DJ Manager to the latest version as soon as a patch is released. If no update is available, disable the plugin until a fix is provided. As a temporary measure, review code for any unserialize() calls handling external input and replace with safer alternatives like json_decode().

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. Verify MDJM plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Mobile DJ Manager' or 'MDJM', or check the /wp-content/plugins/ directory for an mdjm or mobile-dj-manager folder
    Affected if The MDJM Mobile DJ Manager plugin is present in the WordPress installation
  2. Identify the installed MDJM version
    In WordPress admin, click on the MDJM plugin to view its details and note the version number, or check the main plugin PHP file (usually mdjm.php or class-mdjm.php) for a 'Version:' header comment
    Affected if The installed version number is lower than the patched version released for CVE-2025-31074
  3. Confirm the plugin is active
    In WordPress admin > Plugins, verify that MDJM/Mobile DJ Manager shows as 'Active' under the plugin status
    Affected if The plugin is activated and accessible to users
  4. Check for the unsafe deserialization pattern in plugin code
    Search plugin source files for calls to unserialize() on user-supplied data, such as: unserialize($_POST['...']), unserialize($_GET['...']), or unserialize($_REQUEST['...']) - examine files in /wp-content/plugins/mdjm/ directory
    Affected if Code contains unserialize() calls that process untrusted input from GET, POST, or REQUEST superglobals without validation

A user is affected if the MDJM Mobile DJ Manager plugin is installed, active, and running a version that contains the unsafe unserialize() call processing 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 Mobile DJ Manager to the latest version as soon as a patch is released. If no update is available, disable the plugin until a fix is provided. As a temporary measure, review code for any unserialize() calls handling external input and replace with safer alternatives like json_decode().

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation8.0 h
  • Testing8.0 h
  • Review / QA4.0 h
26.0 hours of engineering $4,560
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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