dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-10587

HIGH · 8.8 CVSS v3.1 Published 2024-12-04
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
94/100
Remediation priority · Urgent
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
The Interactive Contact Form and Multi Step Form Builder with Drag & Drop Editor – Funnelforms Free plugin for WordPress is vulnerable to PHP Object Injection in all versions up to, and including, 3.7.5.1 via deserialization of untrusted input. This makes it possible for authenticated attackers, with Contributor-level access and above, to inject a PHP Object. No known POP chain is present in the vulnerable software. If a POP chain is present via an additional plugin or theme installed on the target system, it could allow the attacker to delete arbitrary files, retrieve sensitive data, or execute code.

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 Funnelforms Free WordPress plugin versions up to 3.7.5.1 are vulnerable to PHP Object Injection via unsafe deserialization of untrusted input. Authenticated attackers with Contributor-level access or higher can inject arbitrary PHP objects. While no POP chain exists within the plugin itself, if other installed plugins or themes provide a POP chain, attackers could achieve arbitrary file deletion, data exfiltration, or remote code execution.

MitigationUpdate the Funnelforms Free plugin to a version beyond 3.7.5.1 once available, and audit the WordPress environment for additional plugins or themes that could provide a POP chain for exploitation.

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

CVSS:3.1/AV:N/AC:L/PR:L/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 Funnelforms Free plugin is installed
    Navigate to WordPress admin > Plugins > Installed Plugins and look for 'Funnelforms Free' in the list. Check if it is activated.
    Affected if The plugin is present and activated in the WordPress installation
  2. Determine installed plugin version
    In the Plugins list, click on 'Funnelforms Free' to view details, or check the plugin header in /wp-content/plugins/funnelforms-free/ folder for the version number. Compare this version to 3.7.5.1.
    Affected if The installed version is 3.7.5.1 or lower (any version 'up to 3.7.5.1')
  3. Identify users with Contributor-level or higher access
    Go to WordPress admin > Users and review the role column. Contributor, Author, Editor, and Administrator roles all have the required access level to exploit this vulnerability.
    Affected if Any user account has Contributor, Author, Editor, or Administrator role assigned
  4. Audit for POP chain capable plugins or themes
    Review all active plugins and the active theme for known PHP Object Injection POP chains. Check plugin directories in /wp-content/plugins/ for popular plugins that have historically contained POP chains (e.g., certain versions of WooCommerce, Yoast, Elementor, or commonly exploited theme frameworks).
    Affected if Any additional installed plugin or theme provides a usable POP chain for PHP Object Injection

You are affected if Funnelforms Free version 3.7.5.1 or lower is installed, any Contributor-level or higher user account exists, AND another plugin or theme with a POP chain is present in the environment.

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 the Funnelforms Free plugin to a version beyond 3.7.5.1 once available, and audit the WordPress environment for additional plugins or themes that could provide a POP chain for exploitation.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,060
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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