dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-39480

CRITICAL · 9.8 CVSS v3.1 Published 2025-05-23
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 ThemeMakers Car Dealer cardealer allows Object Injection.This issue affects Car Dealer: from n/a through < 1.6.8.

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 ThemeMakers Car Dealer WordPress plugin/theme allows attackers to inject PHP objects, potentially leading to remote code execution. The vulnerability affects versions prior to 1.6.8.

MitigationUpdate the Car Dealer theme/plugin to version 1.6.8 or later. If no patch is available from the vendor, disable the plugin until a fix is released.

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. Locate the Car Dealer plugin installation
    Check the WordPress plugins directory (wp-content/plugins/) for folders containing 'car-dealer', 'car dealer', or 'thememakers' in the name. Also check the wp_options table for option_name containing 'car_dealer' version information.
    Affected if The Car Dealer plugin by ThemeMakers is not found in the expected locations.
  2. Identify the installed plugin version
    Open the main plugin PHP file (usually the primary PHP file in the plugin folder) and locate the 'Version' header in the plugin comment block, or check the WordPress admin plugin list for the installed version number.
    Affected if Unable to determine the version number from the plugin files or admin interface.
  3. Compare version against the fixed release
    Compare the installed version number to 1.6.8. Any version below 1.6.8 (such as 1.6.7, 1.6.6, 1.5.x, etc.) is considered vulnerable.
    Affected if The installed version is lower than 1.6.8 (for example, 1.6.7 or earlier).
  4. Verify deserialization handling in plugin code
    Search plugin PHP files for usage of unserialize() function, particularly where $_GET, $_POST, $_REQUEST, or other user-supplied input is passed directly to unserialize() without validation.
    Affected if The plugin code contains unserialize() calls processing user input without sanitization.
  5. Check for available PHP classes with magic methods
    Review installed plugins and themes for classes containing __wakeup, __destruct, __call, or __toString magic methods, which could be exploited for POP chain attacks if combined with the deserialization flaw.
    Affected if Additional plugins or themes contain exploitable classes with magic methods in the application scope.

You are affected if the ThemeMakers Car Dealer plugin is installed with a version lower than 1.6.8 and the plugin processes user-controlled data through PHP deserialization functions.

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 Car Dealer theme/plugin to version 1.6.8 or later. If no patch is available from the vendor, disable the plugin until a fix is released.

Recommended fix Moderate confidence

1.6.8 or later

  1. 1. Log in to the WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Locate the 'Car Dealer' (cardealer) plugin by ThemeMakers
  4. 4. If the plugin shows a version lower than 1.6.8, click 'Update Now' to upgrade to version 1.6.8 or latest available version
  5. 5. After updating, verify the plugin version is 1.6.8 or higher
  6. 6. Test critical functionality on the site to ensure the update did not cause issues

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

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,390
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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