dbcve.org
Deserialization of Untrusted DataWeakness · CWE-502

CVE-2024-4471

HIGH · 8.0 CVSS v3.1 Published 2024-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 →
84/100
Remediation priority · High
Remotely reachable

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 140+ Widgets | Best Addons For Elementor – FREE for WordPress is vulnerable to PHP Object Injection in versions up to, and including, 1.4.3.1 via deserialization of untrusted input in the 'export_content' function. This allows authenticated attackers, with contributor-level permissions and above, to inject a PHP Object. No POP chain is present in the vulnerable plugin. 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. Thanks, Francesco

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 WordPress plugin '140+ Widgets | Best Addons For Elementor' versions up to 1.4.3.1 is vulnerable to PHP Object Injection through unsafe deserialization of user-supplied data in the 'export_content' function. Authenticated attackers with contributor-level permissions or higher can inject arbitrary PHP objects. While no POP chain exists within the plugin itself, a POP chain from another installed plugin or theme could enable remote code execution, arbitrary file deletion, or sensitive data exfiltration.

MitigationUpdate the plugin to the latest version beyond 1.4.3.1 immediately. Until updated, restrict contributor-level access and audit installed plugins/themes for potential POP chains that could be chained with this vulnerability.

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:R/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. Locate the plugin in your WordPress installation
    Check your wp-content/plugins directory for a folder related to '140+ Widgets | Best Addons For Elementor'. The folder may be named something like 'ultimate-addons-for-elementor' or similar. Also check the WordPress admin under Plugins > Installed Plugins for this plugin.
    Affected if The plugin folder exists in wp-content/plugins or the plugin appears in your WordPress admin plugin list.
  2. Determine the installed version
    In WordPress admin, go to Plugins > Installed Plugins and look for the version number listed under the plugin name. Alternatively, open the main plugin PHP file (usually named similarly to the folder) and look for a 'Version' comment or defined constant near the top.
    Affected if The version listed is 1.4.3.1 or lower.
  3. Verify the vulnerable function exists
    In the plugin folder, search for the string 'export_content' in PHP files. This function contains the unsafe deserialization call. You can use grep: grep -r "export_content" /path/to/wp-content/plugins/PLUGIN_FOLDER/
    Affected if A function named 'export_content' is found that contains unserialize() or similar deserialization logic.
  4. Confirm the plugin is active
    In WordPress admin > Plugins > Installed Plugins, check if the plugin is currently activated. Alternatively, query your WordPress database: SELECT option_value FROM wp_options WHERE option_name = 'active_plugins';
    Affected if The plugin appears in the list of active plugins.
  5. Assess user role exposure
    In WordPress admin > Users, review which users have roles of Contributor, Author, Editor, or Administrator. These roles meet the minimum permission level for exploiting this vulnerability.
    Affected if There are users with Contributor-level access or higher who can access the site.

You are affected if the plugin is installed, is version 1.4.3.1 or lower, is active, and you have users with contributor-level or higher access.

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 plugin to the latest version beyond 1.4.3.1 immediately. Until updated, restrict contributor-level access and audit installed plugins/themes for potential POP chains that could be chained with this vulnerability.

Have this fixed Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing4.0 h
  • Review / QA2.0 h
11.0 hours of engineering $1,900
Get help mitigating

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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