dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-53572

HIGH · 8.1 CVSS v3.1 Published 2025-08-28
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
90/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 emarket-design WP Easy Contact wp-easy-contact allows Object Injection.This issue affects WP Easy Contact: from n/a through <= 4.0.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 · high confidence

The WP Easy Contact WordPress plugin up to version 4.0.1 is vulnerable to PHP Object Injection via unsafe deserialization of untrusted data. An attacker can supply malicious serialized PHP objects that, when unserialized by the application, may trigger magic method execution leading to arbitrary file deletion, SQL injection, or remote code execution depending on available gadget chains within the WordPress environment.

MitigationReplace unsafe unserialize() calls with json_decode() or other safe deserialization methods; validate and sanitize all user input before deserialization; update to patched version when available.

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

CVSS:3.1/AV:N/AC:H/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. Confirm WP Easy Contact plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'WP Easy Contact' or check the plugins directory at /wp-content/plugins/ for a folder named 'wp-easy-contact' or similar
    Affected if The plugin appears in the installed plugins list
  2. Identify the installed version
    In WordPress admin, click on the plugin name to view details and note the version number, or inspect the main plugin file (e.g., wp-easy-contact.php) and look for a 'Version:' header comment
    Affected if The version is 4.0.1 or lower
  3. Search for unsafe unserialize() calls in plugin code
    Use grep or a file search tool to scan plugin PHP files for 'unserialize(' calls. Check files that handle form submissions, AJAX endpoints, or any file that processes data from $_POST, $_GET, or $_REQUEST
    Affected if Code contains unserialize() calls without prior sanitization
  4. Verify if user input reaches the unserialize() function
    Examine the unserialize() calls found and trace whether parameters come directly from $_POST, $_GET, cookies, or database values without validation through sanitize_text_field(), esc_attr(), or similar functions
    Affected if User-controlled data flows directly into unserialize() without validation
  5. Check for available gadget chains
    Review if other vulnerable plugins or themes are installed that might provide gadget chains for PHP object injection, or check if the site has known POP chains in common libraries
    Affected if Other exploitable plugins/themes exist that could chain with this vulnerability for RCE or file deletion

You are affected if the WP Easy Contact plugin version is 4.0.1 or lower and your site processes user input through unsafe unserialize() calls without sanitization.

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

Replace unsafe unserialize() calls with json_decode() or other safe deserialization methods; validate and sanitize all user input before deserialization; update to patched version when available.

Recommended fix Low confidence
  1. Check WordPress admin panel for available plugin updates for WP Easy Contact
  2. If an update is available, install it to obtain the patched version
  3. If no update is available through WordPress, contact the plugin developer directly for a patched release
  4. Alternatively, disable the WP Easy Contact plugin until a patched version is available
  5. Audit the site for any suspicious activity or unauthorized access since the vulnerability may have been exploited

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-53572 — 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-53572 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