dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-47536

HIGH · 7.2 CVSS v3.1 Published 2025-08-14
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
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 keywordrush Content Egg content-egg allows Object Injection.This issue affects Content Egg: from n/a through <= 7.0.0.

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

The Content Egg WordPress plugin through version 7.0.0 is vulnerable to PHP Object Injection via deserialization of untrusted data. This deserialization flaw allows attackers to inject malicious PHP objects, potentially leading to remote code execution depending on available classes in the application or WordPress environment.

MitigationUpdate to the patched version of Content Egg as soon as available. Until then, disable the plugin or implement strict input validation to prevent untrusted data from reaching deserialization functions.

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
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. Confirm Content Egg plugin is installed
    In WordPress admin, go to Plugins > Installed Plugins and look for 'Content Egg' in the list. Alternatively, check if /wp-content/plugins/content-egg/ directory exists on the server.
    Affected if Content Egg plugin is present in the WordPress installation
  2. Identify installed version
    In WordPress admin_plugins list, the version number is displayed under the plugin name. Alternatively, check the 'readme.txt' or 'content-egg.php' file in the plugin directory for the 'Version' header.
    Affected if Version is 7.0.0 or lower (any version through 7.0.0)
  3. Locate deserialization calls in plugin code
    Search the plugin directory for PHP 'unserialize()' function calls. In command line: grep -r "unserialize" /path/to/wp-content/plugins/content-egg/
    Affected if The plugin contains unserialize() calls that process input from user-accessible sources
  4. Identify input sources reaching deserialization
    Review the code around any unserialize() calls found. Check if data comes from POST/GET parameters, cookies, or API endpoints without sanitization.
    Affected if Untrusted user input (request parameters, headers, or external API responses) flows directly into unserialize() without validation

A user is affected if Content Egg plugin version 7.0.0 or lower is installed AND the plugin processes untrusted data through PHP unserialize() in accessible code paths.

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 to the patched version of Content Egg as soon as available. Until then, disable the plugin or implement strict input validation to prevent untrusted data from reaching deserialization functions.

Have this fixed Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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