dbcve.org
Wp Crm SystemWordPress extension · Wp Crm

CVE-2025-47629

HIGH · 7.2 CVSS v3.1 Published 2025-05-07
Fix available
A fix is available. Upgrade to after 3.4.1 or later.
See remediation →
78/100
Remediation priority · High
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 Mario Peshev WP-CRM System wp-crm-system allows Object Injection.This issue affects WP-CRM System: from n/a through <= 3.4.5.

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 · high confidence

This is a PHP Object Injection vulnerability in the WP-CRM System plugin caused by unsafe deserialization (unserialize()) of untrusted data. Attackers can potentially craft malicious serialized PHP objects to achieve remote code execution if POP (Property-Oriented Programming) chains exist within the plugin or WordPress environment.

MitigationReplace unsafe unserialize() calls with safer alternatives like json_decode() for JSON data, or implement a whitelist of allowed classes if serialization is required. Ensure all user-supplied data is validated before deserialization.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Wp Crm SystemWordPress extension
Affected:<= 3.4.1

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

CVSS:3.1/AV:N/AC:L/PR:H/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 WP-CRM System plugin is installed
    Access WordPress admin dashboard, navigate to Plugins > Installed Plugins, and look for 'WP-CRM System' or 'Wp Crm Wp Crm System' in the list of active plugins
    Affected if The plugin appears in the installed plugins list
  2. Check the installed version number
    In the installed plugins list, locate the version number displayed under the WP-CRM System plugin name, or inspect the main plugin file (typically wp-crm-system.php) and look for the 'Version:' header in the plugin comment block
    Affected if The version is 3.4.1 or any version lower than 3.4.1
  3. Locate unsafe unserialize calls in the plugin
    Using a text editor or grep tool, search all PHP files in the wp-content/plugins/wp-crm-system directory for the pattern 'unserialize(' - examine each occurrence to determine if it processes data from external sources such as $_POST, $_GET, $_REQUEST, or database values
    Affected if The plugin contains unserialize() calls that process untrusted user-supplied data
  4. Confirm attack surface accessibility
    Identify which input vectors (form submissions, REST API endpoints, file imports, or admin AJAX actions) feed data into the vulnerable unserialize() calls found in step 3; test whether these endpoints are accessible to authenticated users or unauthenticated attackers
    Affected if User-controlled data can reach the unsafe unserialize() function without proper validation

A WordPress installation is affected if it runs WP-CRM System version 3.4.1 or lower AND contains code paths where user input flows into unserialize() calls accessible to attackers.

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
Upgrade available Upgrade to a release after 3.4.1
Interim mitigation

Replace unsafe unserialize() calls with safer alternatives like json_decode() for JSON data, or implement a whitelist of allowed classes if serialization is required. Ensure all user-supplied data is validated before deserialization.

Recommended fix High confidence

Latest version beyond 3.4.5 (check WordPress plugin repository for current stable release)

  1. 1. Log in to your WordPress admin dashboard
  2. 2. Navigate to Plugins > Installed Plugins
  3. 3. Find WP-CRM System in the plugin list
  4. 4. If an update is available, click 'Update Now' to update to the latest version
  5. 5. Verify the update completed successfully by checking the plugin version after updating
  6. 6. If no update is available through WordPress, manually download the latest version from the official WordPress plugin repository and reinstall
Caveat Review plugin settings and test core functionality after upgrade to ensure compatibility with your WordPress setup

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

Fix this in Wp Crm System Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing3.0 h
  • Review / QA2.0 h
9.0 hours of engineering $1,570
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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