dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2025-47530

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 WPFunnels WPFunnels wpfunnels allows Object Injection.This issue affects WPFunnels: from n/a through <= 3.5.18.

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 WPFunnels WordPress plugin <= 3.5.18 is vulnerable to PHP Object Injection via deserialization of untrusted data. An unauthenticated attacker can potentially exploit this by passing malicious serialized PHP objects to vulnerable unserialize() calls, which may enable remote code execution if suitable gadget chains exist in the application or surrounding ecosystem.

MitigationUpgrade WPFunnels to version 3.5.19 or later. If a patch is unavailable, disable the plugin until an update is released, as this critical vulnerability is remotely exploitable without authentication.

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. Verify WPFunnels plugin is installed
    Navigate to WordPress admin dashboard > Plugins > Installed Plugins, or inspect the file /wp-content/plugins/ for a folder named 'wpfunnels' or 'funnel-builder'. Alternatively, query the WordPress database: SELECT * FROM wp_options WHERE option_name = 'active_plugins' and check for 'wpfunnels' or 'funnel-builder' in the serialized array.
    Affected if WPFunnels or Funnel Builder plugin appears in the active plugins list.
  2. Determine installed WPFunnels version
    In WordPress admin, go to Plugins > Installed Plugins and locate WPFunnels or Funnel Builder to view the version number. Alternatively, check the main plugin file header at /wp-content/plugins/wpfunnels/wpfunnels.php or /wp-content/plugins/funnel-builder/funnel-builder.php for the 'Version' comment, or query: SELECT option_value FROM wp_options WHERE option_name = 'wpfunnels_version' or similar version option.
    Affected if Unable to determine version or version is displayed.
  3. Compare version against affected range
    If version is obtained from step 2, compare numerically: the vulnerability affects all versions <= 3.5.18. Note that the plugin may also be marketed as 'Funnel Builder' with potentially different version numbering.
    Affected if Installed version is 3.5.18 or lower, or version numbering indicates <= 3.5.18.

If WPFunnels or Funnel Builder plugin is installed, active, and the version is 3.5.18 or lower, the environment is affected by this PHP Object Injection vulnerability and is exploitable by unauthenticated 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
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade WPFunnels to version 3.5.19 or later. If a patch is unavailable, disable the plugin until an update is released, as this critical vulnerability is remotely exploitable without authentication.

Recommended fix Moderate confidence

Latest version beyond 3.5.18 (check WordPress plugin repository or vendor for current stable release)

  1. 1. Backup your WordPress database and files before making any changes
  2. 2. Update WPFunnels plugin to the latest available version from the WordPress plugin repository or the vendor's official source
  3. 3. Verify the update was successful by checking the installed version number
  4. 4. Test critical funnel flows to ensure functionality remains intact after the update
  5. 5. Monitor for any unusual behavior or errors following the update
Caveat Review plugin changelog for any breaking changes between your current version and the new version

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 / QA1.0 h
10.0 hours of engineering $1,750
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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